CVERadar
HIGH · CVSS 3.1 8.1CISA KEV · added 2022-03-25Metasploit moduleExploit-DBPublic PoCEPSS 99.97% (p100)Threat level 85

CVE-2017-12617: Apache Tomcat Remote Code Execution Vulnerability

Apache · Tomcat · NVD published 2017-10-04 · posted 2026-10-21 · last modified 2026-08-25

What it is

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.

WeaknessCWE-434
CVSS vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (source: [email protected])
CISA due date2022-04-15 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsInitial Access → Persistence

Exploitation evidence

First exploit evidence seen: 2017-10-03 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2022-03-25. Source

Public exploit code

Metasploit

Exploit-DB

  • EDB-42966: Apache Tomcat < 9.0.1 (Beta) / < 8.5.23 / < 8.0.47 / < 7.0.8 - JSP Upload Bypass / Remote Code Execution (2) (2017-10-09, verified)
  • EDB-43008: Tomcat - Remote Code Execution via JSP Upload Bypass (Metasploit) (2017-10-17, verified)

GitHub proof-of-concept repositories

10 public repositories from 10 accounts, first seen 2017-10-05. Most starred: cyberheartmi9/CVE-2017-12617 (401 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · Rapid7 Metasploit Framework module metadata · Exploit-DB (OffSec) · nomi-sec/PoC-in-GitHub.

Defend the Chain

The attack chain for CVE-2017-12617 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 85/100
Defender level 1 · 0 XP
Chain links broken: 0/2

Reconnaissance

Resource Development

Initial Access

Execution

Persistence

Privilege Escalation

Stealth

Defense Impairment

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1190 Exploit Public-Facing Application Inferred

Inferred from CWE CWE-434

How to fix it

CISA required action

Apply updates per vendor instructions. (source: CISA KEV)

Fixed versions

  • apache tomcat: upgrade to 7.0.82 or later (affected from 7.0.0)
  • apache tomcat: upgrade to 8.0.47 or later (affected from 8.0)
  • apache tomcat: upgrade to 8.5.23 or later (affected from 8.5.0)
  • apache tomcat: upgrade to 9.0.1 or later (affected from 9.0.0)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

MITRE ATT&CK mitigations for this chain

  • M1048 Application Isolation and Sandboxing (for T1190) : Application isolation will limit what other processes and system features the exploited target can access.
  • M1037 Filter Network Traffic (for T1190) : Restrict outbound network traffic from public-facing servers to prevent unauthorized connections from initiating communications with attacker-controlled infrastructure. While this may not prevent the initial exploitation, it limits the attacker's ability to verify and control the compromised server post-exploit, reduci
  • M1030 Network Segmentation (for T1190) : Segment externally facing servers and services from the rest of the network with a DMZ or on separate hosting infrastructure.
  • M1016 Vulnerability Scanning (for T1190) : Regularly scan externally facing systems for vulnerabilities and establish procedures to rapidly patch systems when critical vulnerabilities are discovered through scanning and through public disclosure.
  • M1026 Privileged Account Management (for T1190) : Use least privilege for service accounts will limit what permissions the exploited process gets on the rest of the system.
  • M1050 Exploit Protection (for T1190) : Web Application Firewalls may be used to limit exposure of applications to prevent exploit traffic from reaching the application.
  • M1035 Limit Access to Resource Over Network (for T1190) : Ensure that all publicly exposed services are actually intended to be so, and restrict access to any that should only be available internally.
  • M1051 Update Software (for T1190) : Update software regularly by employing patch management for externally exposed applications.
  • M1042 Disable or Remove Feature or Program (for T1505.003) : Consider disabling functions from web technologies such as PHP’s `evaI()` that may be abused for web shells.
  • M1018 User Account Management (for T1505.003) : Enforce the principle of least privilege by limiting privileges of user accounts so only authorized accounts can modify the web directory.

Detection Generic guidance

  • Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
  • Persistence: Look for new files in web roots, new scheduled tasks/services, and new accounts created after the exposure window.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Sources