CVE-2017-12617
KEVApache Tomcat Remote Code Execution Vulnerability
Description
When running Apache Tomcat, it is 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.
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.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HPublishedOct 4, 2017
Last modifiedAug 25, 2026
Added to KEVMar 25, 2022
Remediation dueApr 15, 2022
References
- oracle.com/technetwork/security-advisory/cpuapr2018-3678067.htmlPatchThird Party Advisory
- oracle.com/technetwork/security-advisory/cpujan2018-3236628.htmlPatchThird Party Advisory
- oracle.com/technetwork/security-advisory/cpujul2018-4258247.htmlPatchThird Party Advisory
- securityfocus.com/bid/100954Broken LinkThird Party Advisory
- securitytracker.com/id/1039552Broken LinkThird Party Advisory
- access.redhat.com/errata/RHSA-2017:3080Third Party Advisory
- access.redhat.com/errata/RHSA-2017:3081Third Party Advisory
- access.redhat.com/errata/RHSA-2017:3113Third Party Advisory
- access.redhat.com/errata/RHSA-2017:3114Third Party Advisory
- access.redhat.com/errata/RHSA-2018:0268Third Party Advisory
- access.redhat.com/errata/RHSA-2018:0269Third Party Advisory
- access.redhat.com/errata/RHSA-2018:0270Third Party Advisory
0 recent articles mention this CVE
80
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1656 days
- CVSS
- 8.1 HIGH
- EPSS (30-day exploit probability)
- 100.0% · top 1% of all CVEs
- Weakness
- CWE-434
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.Apply updates per vendor instructions.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.