StrutsFramework / library · Apache
CVE-2017-9805
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe REST Plugin in Apache Struts 2.1.1 through 2.3.x before 2.3.34 and 2.5.x before 2.5.13 uses an XStreamHandler with an instance of XStream for deserialization without any type filtering, which can lead to Remote Code Execution when deserializing XML payloads.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Apache Struts 2 REST Plugin uses XStreamHandler with an instance of XStream for deserializing XML payloads without any type filtering. This allows remote attackers to execute arbitrary code by sending specially crafted XML that exploits the unsafe deserialization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
StrutsFramework / library
>= 2.1.2, < 2.3.34>= 2.5.0, < 2.5.13
Digital Media ManagerApplication
all versions
Hosted Collaboration SolutionApplication
= 10.5\(1\)= 11.0\(1\)= 11.5\(1\)= 11.6\(1\)
Media Experience EngineApplication
= 3.5= 3.5.2
Network Performance AnalysisApplication
all versions
Video Distribution Suite For Internet StreamingApplication
all versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Struts versionLocate the struts2-core JAR file in your application deployment (typically in WEB-INF/lib) and check the filename for the version number, or examine the manifest file inside the JAR. On Linux, you can run: find /path/to/deployment -name 'struts2-core*.jar' -exec basename {} \;Affected if The installed version is 2.1.2 through 2.3.33, or 2.5.0 through 2.5.12
-
Check if REST plugin is deployedSearch for the struts2-rest-plugin.jar in your application deployment directory (WEB-INF/lib). On Linux: find /path/to/deployment -name 'struts2-rest-plugin*.jar'Affected if The struts2-rest-plugin.jar file exists in the deployed application
-
Verify REST plugin is configured in struts.xmlExamine the struts.xml configuration file (typically in WEB-INF/classes) and look for the <package> declarations that extend 'rest-default' or include the REST plugin result types and interceptors. Also check for any <result-types> using XStreamHandler.Affected if The struts.xml contains configurations that extend the REST plugin package or reference rest-default
-
Confirm XStreamHandler is in use for XML endpointsReview struts.xml for XStreamHandler configuration in <result-type> definitions, or check the REST plugin's content-type handlers. Look for XML-based REST endpoints (urls ending in .xml or with Accept: application/xml) that the application serves.Affected if The application exposes XML endpoints through the REST plugin that use XStream for deserialization
-
Check for custom type filtering (mitigation applied)Examine the struts.xml for any explicitly configured <param name="strictDMI">false</param> settings, or check if there are custom type whitelisting configurations for XStream. Also review any custom interceptor or filter that may have been added to restrict deserialization types.Affected if No type filtering is configured and the REST plugin XML deserialization remains exposed without restrictions
Your environment is affected if Apache Struts versions 2.1.2-2.3.33 or 2.5.0-2.5.12 are installed with the REST plugin enabled and configured to handle XML requests via XStreamHandler.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.3.342.5.13
Upgrade to Apache Struts 2.3.34 or 2.5.13 or later, which implement type filtering for XStream deserialization in the REST plugin.
Apache Struts 2.3.34 or 2.5.13 (or later stable releases within those branches)
- 1. Identify the current Apache Struts version by examining the struts2-core.jar file in your application or checking your dependency management system (Maven, Gradle, etc.)
- 2. For Struts 2.3.x users: Upgrade to Struts 2.3.34 or later (recommended: latest 2.3.x release)
- 3. For Struts 2.5.x users: Upgrade to Struts 2.5.13 or later (recommended: latest 2.5.x release)
- 4. If using Maven, update the struts2-core dependency version in your pom.xml to the target version
- 5. Replace all Struts JAR files in your application deployment (lib folder) with the new version
- 6. Re-deploy the application and restart the application server
- 7. Verify that the REST plugin functionality works correctly and that the vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Struts
Exploited in the wild — priority engagement
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-9805 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data