Is CVE-2017-12617 exploited in the wild?

Yes. CVE-2017-12617 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.

How severe is CVE-2017-12617?

Critical severity, with a CVSS score of 3, published 14 May 2022.

Which products and versions are affected?

org.apache.tomcat:tomcat-catalina (Maven) ECOSYSTEM:introduced=9.0.0.M1,fixed=9.0.1; org.apache.tomcat.embed:tomcat-embed-core (Maven) ECOSYSTEM:introduced=9.0.0.M1,fixed=9.0.1.

How is CVE-2017-12617 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2017-12617?

Check whether you run Apache Tomcat, org.apache.tomcat:tomcat-catalina (Maven) or org.apache.tomcat.embed:tomcat-embed-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2017-12617: Unrestricted Upload of File with Dangerous Type Apache Tomcat

CVE-2017-12617 · Severity: critical · CVSS 3 · Exploited in the wild · Published 2022-05-14

Apache Tomcat allows remote code execution when HTTP PUT requests are enabled. An attacker can upload a specially crafted JSP file to the server, which can then be executed by requesting the file.

Technologies: Apache Tomcat, org.apache.tomcat:tomcat-catalina (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven). Vendors: Apache, Maven.

Quick answers

Is CVE-2017-12617 exploited in the wild?: Yes. CVE-2017-12617 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.
How severe is CVE-2017-12617?: Critical severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?: org.apache.tomcat:tomcat-catalina (Maven) ECOSYSTEM:introduced=9.0.0.M1,fixed=9.0.1; org.apache.tomcat.embed:tomcat-embed-core (Maven) ECOSYSTEM:introduced=9.0.0.M1,fixed=9.0.1.
Is there a fix for CVE-2017-12617?: Yes. org.apache.tomcat:tomcat-catalina (Maven): upgrade to 9.0.1 or later; org.apache.tomcat.embed:tomcat-embed-core (Maven): upgrade to 9.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-12617 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2017-12617?: Check whether you run Apache Tomcat, org.apache.tomcat:tomcat-catalina (Maven) or org.apache.tomcat.embed:tomcat-embed-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.apache.tomcat:tomcat-catalina (Maven): upgrade to 9.0.1 or later

# set org.apache.tomcat:tomcat-catalina to 9.0.1 in your pom.xml or build.gradle

org.apache.tomcat.embed:tomcat-embed-core (Maven): upgrade to 9.0.1 or later

# set org.apache.tomcat.embed:tomcat-embed-core to 9.0.1 in your pom.xml or build.gradle

Affected products

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

Identifiers

CVE-2017-12617
GHSA-xjgh-84hx-56c5

Timeline

2022-03-25: disclosed: Publication date of the advisory.
exploited: Reported as exploited in the wild.

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.