CVE-2017-12615
Redhat Enterprise Linux Eus 7.4 … 7.7
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2017-12615 is a high-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Redhat Enterprise Linux Eus. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability tracked as CVE-2017-12615 affects Apache Tomcat versions 7.0.0 through 7.0.79 running on Windows when the DefaultServlet is configured with its readonly initialization parameter set to false, enabling HTTP PUT requests. This configuration permits an attacker to upload a JSP file through a specially crafted request; once uploaded, the JSP can be accessed and executed by the server, resulting in arbitrary code execution. The issue is classified under CWE-434 and carries a CVSS 3.1 score of 8.1.
An unauthenticated remote attacker can exploit the flaw over the network by sending the crafted PUT request to upload a malicious JSP payload and then invoking it to execute code. Successful exploitation grants full control over the affected Tomcat instance, impacting confidentiality, integrity, and availability, although the attack requires the non-default PUT capability to be enabled and therefore receives a high attack-complexity rating.
Red Hat has published errata RHSA-2017:3080 and RHSA-2017:3081 that address the issue for supported products; additional details appear in vendor trackers such as SecurityFocus and SecurityTracker.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2018-0654
Vulnerability Data
When running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default to false) it was possible to upload a JSP file to the server via a specially crafted…
more
request. This JSP could then be requested and any code it contained would be executed by the server.
- CWE(s)
- KEV Date Added
- 25 March 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requiring identifiable owners for portable devices reduces the attack surface for unrestricted uploads of dangerous file types via anonymous media.
Dangerous file uploads can be detonated in the chamber to determine malice before any production write or execution occurs.
Prevents unrestricted writing of arbitrary or malicious firmware by keeping hardware write-protect enabled except under tightly controlled manual procedures.
Scans files from external sources on download/open/execute, blocking unrestricted uploads of dangerous file types.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Hardened configuration baselines can enforce allowed file types and processing rules.
Secure development practices include input validation and file-type restrictions that prevent this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.
Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.
Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.
Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.