# CVE-2017-12615: When running Apache Tomcat on Windows with HTTP PUTs enabled it was possible to upload a JSP file to the server

Source: https://junglewise.ai/threats/cve-2017-12615-apache-tomcat-on-windows-remote-code-execution-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2018-10-17. Updated: 2026-05-10  
License: CC BY 4.0 with a link back

CVE-2017-12615 · Severity: critical · CVSS 3 · Exploited in the wild · Published 2018-10-17

Apache Tomcat on Windows allows remote code execution when HTTP PUT is enabled. An attacker can upload a specially crafted JSP file to the server, which can then be executed by the server upon request.

Technologies: [Apache Tomcat](https://junglewise.ai/threats/technologies/tomcat), [org.apache.tomcat.embed:tomcat-embed-core (Maven)](https://junglewise.ai/threats/technologies/org-apache-tomcat-embed-tomcat-embed-core). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache), [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

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

**How severe is CVE-2017-12615?** Critical severity, with a CVSS score of 3, published 17 October 2018.

**Which products and versions are affected?** org.apache.tomcat.embed:tomcat-embed-core (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.0.79.

**Is there a fix for CVE-2017-12615?** Yes. org.apache.tomcat.embed:tomcat-embed-core (Maven): upgrade to 7.0.79 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2017-12615 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2017-12615?** Check whether you run Apache Tomcat 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.embed:tomcat-embed-core (Maven): upgrade to 7.0.79 or later

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


## Affected products

- Apache Tomcat 7.0.0 to 7.0.79

## Identifiers

- CVE-2017-12615
- GHSA-pjfr-qf3p-3q25

## Timeline

- 2017-09-19: disclosed: Initial public disclosure and exploit availability.
- 2022-03-25: kev added: Added to CISA Known Exploited Vulnerabilities Catalog.

## Related threats

- [Apache Tomcat Jakarta Security credential handler bypass](https://junglewise.ai/threats/cve-2026-111248-the-jakarta-security-identity-store-backed-by-the-tomcat-user)
- [Apache Tomcat incomplete cleanup in TLS 1.3 connections](https://junglewise.ai/threats/cve-2026-93446-incomplete-cleanup-vulnerability-in-apache-tomcat-could-cause-tls)
- [Apache Tomcat HTTP trailer information leak between requests](https://junglewise.ai/threats/cve-2026-88041-incomplete-cleanup-vulnerability-in-apache-tomcat-allowed-an)
- [Apache Tomcat TOCTOU race condition in APR/Native connector](https://junglewise.ai/threats/cve-2026-80353-time-of-check-time-of-use-toctou-race-condition-vulnerability-in)
- [Apache Tomcat Execution After Redirect vulnerability](https://junglewise.ai/threats/cve-2026-74049-execution-after-redirect-ear-vulnerability-in-apache-tomcat-this)