CVE-2017-12617

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Apache Tomcat. For every flaw being used in attacks, see Exploited flaws; for Apache’s, see Apache flaws being used in attacks.

CVE-2017-12617 is a security flaw in Apache Tomcat, a server for running Java web applications. Attackers can run their own code on Apache Tomcat. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 25 Mar 2022.[1]

Apache Tomcat is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Apache has published a fix or advice.

Description

CISA calls it a remote code execution in Apache Tomcat. In its words: “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.”[1]

The CVE record adds: “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.”[2]

The underlying weakness is unrestricted file upload (CWE-434), in MITRE’s list of common software weaknesses.

It scores 8.1 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Apache’s advisory has them[3]. CISA names the product as Apache Tomcat.

Most families won’t have Apache Tomcat; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 25 Mar 2022, 1,633 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 15 Apr 2022 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at over 99%. That’s in the top 1% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Apache has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[1]

  1. Check whether you use it.Apache Tomcat is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 15 Apr 2022 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 8.1.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at over 99%.[4]

See also

Other Apache Tomcat flaws

Other Apache flaws

  • CVE-2016-3081, Apache Struts: command injection ·
  • CVE-2026-34197, Apache ActiveMQ: improper input validation ·
  • CVE-2024-38475, Apache HTTP Server: improper escaping of output ·
  • CVE-2024-45195, Apache OFBiz: forced browsing ·
  • CVE-2024-27348, Apache HugeGraph-Server: improper access control ·

Other unrestricted file upload flaws

  • CVE-2026-48356, Adobe Commerce and Magento: unrestricted upload of file with dangerous type ·
  • CVE-2026-56291, Balbooa Forms: unrestricted upload of file with dangerous type ·
  • CVE-2026-48939, iCagenda: unrestricted upload of file with dangerous type ·
  • CVE-2026-48908, JoomShaper SP Page Builder: unrestricted upload of file with dangerous type ·
  • CVE-2024-7694, TeamT5 ThreatSonar Anti-Ransomware: unrestricted upload of file with dangerous type ·

Added the same day

  • CVE-2022-26318, WatchGuard Firebox and XTM Appliances: arbitrary code execution ·
  • CVE-2022-26143, Mitel MiCollab, MiVoice Business Express: access control ·
  • CVE-2022-21999, Microsoft Windows: print spooler privilege escalation ·
  • CVE-2021-42237, Sitecore XP: remote command execution ·
  • CVE-2021-22941, Citrix ShareFile: improper access control ·

Every Apache flaw on CISA’s list · Everything added in March 2022

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Apache Tomcat Remote Code Execution Vulnerability”. Known Exploited Vulnerabilities Catalog, added 25 Mar 2022.
  2. ^ National Institute of Standards and Technology. “CVE-2017-12617 Detail”. National Vulnerability Database, published 4 Oct 2017.
  3. ^ Apache. Advisories and fixes: lists.apache.org, lists.apache.org, lists.apache.org, lists.apache.org, lists.apache.org, and 3 more on NVD’s record.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 1.000, percentile 100.0, 31 Oct 2026.
  5. CVE Program. “CVE-2017-12617”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.