# CVE-2017-12617: Apache Tomcat Remote Code Execution > Attackers can upload and execute malicious JSP files on Apache Tomcat servers if HTTP PUT is enabled, leading to remote code execution. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV) - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Oct 2017 - **Updated:** 21 Oct 2025 - **Also known as:** DLA-1166-1, GHSA-xjgh-84hx-56c5, MGASA-2017-0400, UBUNTU-CVE-2017-12617 ## What is CVE-2017-12617? CVE-2017-12617 is a high-severity vulnerability in Apache Tomcat, published on 3 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type) ## Which versions are affected by CVE-2017-12617? 16 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core and org.apache.tomcat:tomcat-catalina. It affects 58 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 7.0.0 | 7.0.82 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 7.0.0 | 7.0.82 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.0.0-RC1 | 8.0.47 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.0.0-RC1 | 8.0.47 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.23 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.23 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0.M1 | 9.0.1 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0.M1 | 9.0.1 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 7.0.0 | 7.0.82 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 7.0.0 | 7.0.82 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.0.0-RC1 | 8.0.47 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.0.0-RC1 | 8.0.47 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 | 8.5.23 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 | 8.5.23 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0.M1 | 9.0.1 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0.M1 | 9.0.1 | Products: Apache Tomcat, Canonical Ubuntu Linux, Debian Debian Linux, Netapp Active Iq Unified Manager, Netapp Element, Netapp Oncommand Balance, Netapp Oncommand Insight, Netapp Oncommand Shift, Netapp Oncommand Workflow Automation, Netapp Snapcenter, Oracle Agile Product Lifecycle Management, Oracle Communications Instant Messaging Server, Oracle Endeca Information Discovery Integrator, Oracle Enterprise Manager for Mysql Database, Oracle Financial Services Analytical Applications Infrastructure, Oracle Fmw Platform, Oracle Health Sciences Empirica Inspections, Oracle Hospitality Guest Access, Oracle Instantis Enterprisetrack, Oracle Management Pack and 38 more. ## How do I fix CVE-2017-12617? Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 7.0.82, 8.0.47, 8.5.23 or 9.0.1. US federal agencies must fix it by 15 Apr 2022. ## Is CVE-2017-12617 being exploited? Yes. Attackers have exploited CVE-2017-12617 in the wild since at least 25 Mar 2022. Public exploit code: - Apache Tomcat < 9.0.1 (Beta) / < 8.5.23 / < 8.0.47 / < 7.0.8 - JSP Upload Bypass / Remote Code Execution (github_poc): https://github.com/cyberheartmi9/CVE-2017-12617 - CVE-2017-12617 is a critical vulnerability leading to Remote Code Execution (RCE) in Apache Tomcat. (github_poc): https://github.com/LongWayHomie/CVE-2017-12617 - Proof of Concept - RCE Exploitation : Web Shell on Apache Tomcat - Ensimag January 2018 (github_poc): https://github.com/ygouzerh/CVE-2017-12617 - Apache Tomcat < 9.0.1 (Beta) / < 8.5.23 / < 8.0.47 / < 7.0.8 - JSP Upload Bypass / Remote Code Execution for Python3 (github_poc): https://github.com/tyranteye666/tomcat-cve-2017-12617 - An implementation of CVE-2017-12617 (github_poc): https://github.com/jptr218/tc_hack - Tomcat RCE via JSP Upload Bypass (metasploit) ## Other vulnerabilities in Apache Tomcat - [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild) - [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild) - [CVE-2026-65637](https://insights.sbomify.com/CVE-2026-65637/): Apache Tomcat: HTTP/2 no-authority bypass of strict SNI validation - CVE-2026-32990 fix incomplete (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-12617 and fix it if it is affected. What it is: CVE-2017-12617 is a high-severity vulnerability in Apache Tomcat, published on 3 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2017-12617 in the wild since at least 25 Mar 2022. Affected packages and fixed versions: - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 7.0.0; fixed in 7.0.82 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 7.0.0; fixed in 7.0.82 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.0.0-RC1; fixed in 8.0.47 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.0.0-RC1; fixed in 8.0.47 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.23 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.23 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0.M1; fixed in 9.0.1 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0.M1; fixed in 9.0.1 - org.apache.tomcat:tomcat-catalina (Maven): affected from 7.0.0; fixed in 7.0.82 - org.apache.tomcat:tomcat-catalina (Maven): affected from 7.0.0; fixed in 7.0.82 - org.apache.tomcat:tomcat-catalina (Maven): affected from 8.0.0-RC1; fixed in 8.0.47 - org.apache.tomcat:tomcat-catalina (Maven): affected from 8.0.0-RC1; fixed in 8.0.47 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-12617/ (Markdown: https://insights.sbomify.com/CVE-2017-12617/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-12617 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-12617 - OSV: https://osv.dev/vulnerability/CVE-2017-12617 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-12617/ Summaries are generated and may contain mistakes; the official description above is the record.