CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighFixed-version data available

CVE-2017-12617 remediation guide

Apache Tomcat

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.

Open CVE record
ProductApache Tomcat
Affected versions9.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, >= 7.0.0 < 7.0.82, >= 8.0 < 8.0.47, >= 8.5.0 < 8.5.23, >= 9.0.0 < 9.0.1, 12.04, 16.04, 17.10, 18.04, 9.3.3, 9.3.4, 9.3.5, 9.3.6, 10.0.1, 3.1.0, 3.2.0, 12.1.0.4.0
Fixed versions7.0.82, 8.0.47, 8.5.23, 9.0.1
Priority basisImmediate · CVSS 8.1 · EPSS 100.0%
01

Identify the affected asset

Confirm whether Apache Tomcat is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 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, >= 7.0.0 < 7.0.82, >= 8.0 < 8.0.47, >= 8.5.0 < 8.5.23, >= 9.0.0 < 9.0.1, 12.04, 16.04, 17.10, 18.04, 9.3.3, 9.3.4, 9.3.5, 9.3.6, 10.0.1, 3.1.0, 3.2.0, 12.1.0.4.0. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.