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

CVE-2017-5638 remediation guide

Apache Struts

The Jakarta Multipart parser in Apache Struts 2 2.3.x before 2.3.32 and 2.5.x before 2.5.10.1 has incorrect exception handling and error-message generation during file-upload attempts, which allows remote attackers to execute arbitrary commands via a crafted Content-Type, Content-Disposition, or Content-Length HTTP header, as exploited in the wild in March 2017 with a Content-Type header containing a #cmd= string.

Open CVE record
ProductApache Struts
Affected versions2.3.x before 2.3.32, 2.5.x before 2.5.10.1, >= 2.2.3 < 2.3.32, >= 2.5.0 < 2.5.10.1, 7.7.1.6, 7.8.1.0, 9.1.0, 10.0.0, 10.1.0, 10.2.0, 10.5.0, 10.3.6.0.0, 12.1.3.0.0, 12.2.1.1.0, 12.2.1.2.0, < 6.6.5
Fixed versions2.3.32, 2.5.10.1, 6.6.5
Priority basisImmediate · CVSS 9.8 · EPSS 100.0%
01

Identify the affected asset

Confirm whether Apache Struts 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: 2.3.x before 2.3.32, 2.5.x before 2.5.10.1, >= 2.2.3 < 2.3.32, >= 2.5.0 < 2.5.10.1, 7.7.1.6, 7.8.1.0, 9.1.0, 10.0.0, 10.1.0, 10.2.0, 10.5.0, 10.3.6.0.0, 12.1.3.0.0, 12.2.1.1.0, 12.2.1.2.0, < 6.6.5. 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.

CVE-2017-5638 Remediation Guide | SECUFOCUS NOW