StrutsFramework / library · Apache
CVE-2013-2115
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 · uneditedApache Struts 2 before 2.3.14.2 allows remote attackers to execute arbitrary OGNL code via a crafted request that is not properly handled when using the includeParams attribute in the (1) URL or (2) A tag. NOTE: this issue is due to an incomplete fix for CVE-2013-1966.
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 confidenceOGNL injection vulnerability in Apache Struts 2 where the includeParams attribute in URL and A tags fails to properly sanitize user input, allowing remote attackers to inject and execute arbitrary OGNL expressions on the server. This is a remote code execution flaw and an incomplete fix for CVE-2013-1966.
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.0.0, <= 2.3.14.1CVSS 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 Struts 2 versionLocate the struts2-core-[version].jar file in your application's classpath, lib directory, or WAR file. Extract or view the JAR filename to determine the version number.Affected if The version is between 2.0.0 and 2.3.14.1 inclusive (for example, 2.3.14 or 2.3.7)
-
Search JSP files for URL tags with includeParamsSearch your application's JSP files for the pattern <s:url includeParams= or <s:a includeParams= where the attribute value is 'get', 'all', or any non-none value.Affected if Any JSP file contains URL or A tags with the includeParams attribute set to a value that allows user-controlled parameters to be included in the generated URL
-
Check for dynamic parameter usage in tagsReview the identified JSP files to determine whether the includeParams attribute uses dynamic values (such as <s:url includeParams="%{parameters.includeParams}">) that could be influenced by user-supplied request parameters.Affected if The includeParams value is set dynamically using OGNL expressions that could be manipulated through HTTP request parameters
You are affected if your installed Struts 2 version is between 2.0.0 and 2.3.14.1 AND your application uses URL or A tags with the includeParams attribute that can accept user-supplied parameter input.
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.
From vendor dataUpgrade Apache Struts 2 to version 2.3.14.2 or later. If immediate upgrading is not feasible, disable or avoid using the includeParams attribute in URL and A tags until the upgrade can be completed.
Fix this in Struts
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2115 — 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-2013-2115 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