StrutsFramework / library · Apache
CVE-2013-2248
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 · uneditedMultiple open redirect vulnerabilities in Apache Struts 2.0.0 through 2.3.15 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in a parameter using the (1) redirect: or (2) redirectAction: prefix.
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 confidenceApache Struts 2 versions 2.0.0 through 2.3.15 contain open redirect vulnerabilities in the redirect: and redirectAction: prefix parameters. Attackers can craft malicious URLs that redirect users to arbitrary external websites, enabling phishing campaigns. The vulnerability stems from insufficient validation of user-supplied redirect targets.
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.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9= 2.0.10= 2.0.11CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
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 2 library versionLocate the struts2-core.jar file in your application WEB-INF/lib directory. Check the MANIFEST.MF file inside the JAR for the Implementation-Version attribute, or use your build system/pom.xml to confirm the Struts version dependency.Affected if The installed version is between 2.0.0 and 2.3.15 inclusive.
-
Verify use of redirect result typesSearch your struts.xml, struts-default.xml, and action Java classes for occurrences of 'redirect:' or 'redirectAction:' result type declarations.Affected if The application uses redirect: or redirectAction: result types in any action configuration.
-
Inspect redirect parameter handling in application codeReview action classes and interceptors that process the 'redirect:' or 'redirectAction:' parameters. Check if user-supplied input (query parameters, form inputs) is used to build the redirect target without validation.Affected if User-controlled input can influence the redirect target without server-side validation allowing arbitrary external URLs.
-
Check web server or WAF logs for suspicious redirect patternsReview access logs for URLs containing redirect: or redirectAction: parameters with external domains (http://, https://) or patterns like 'redirect:http'.Affected if Requests with external URLs in redirect parameters are being processed by the application.
You are affected if your Apache Struts 2 version is between 2.0.0 and 2.3.15 and your application uses redirect: or redirectAction: result types with user-influenced redirect targets.
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.15.1 or later, which contains the patched version. If immediate patching is not feasible, implement URL validation at the application proxy or web application firewall layer to block suspicious redirect patterns.
Fix this in Struts
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2248 — 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-2248 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