Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 21 Jul 2022.
StrutsFramework / library · Apache

CVE-2006-1547

HIGH · 7.5 CVSS v3.1 Published 2006-03-30
Fix available
A fix is available. Upgrade to 1.2.9 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
ActionForm in Apache Software Foundation (ASF) Struts before 1.2.9 with BeanUtils 1.7 allows remote attackers to cause a denial of service via a multipart/form-data encoded form with a parameter name that references the public getMultipartRequestHandler method, which provides further access to elements in the CommonsMultipartRequestHandler implementation and BeanUtils.

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 confidence

CVE-2006-1547 is a vulnerability in Apache Struts before version 1.2.9 that allows remote attackers to cause a denial of service by exploiting a multipart/form-data encoded form. The vulnerability arises from a parameter name that references the public getMultipartRequestHandler method, leading to further access to elements in the CommonsMultipartRequestHandler implementation and BeanUtils.

MitigationTo remediate this vulnerability, upgrade to Apache Struts version 1.2.9 or later. Additionally, review and sanitize input parameters in multipart/form-data requests to prevent exploitation.

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
Affected:< 1.2.9

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed version of Apache Struts
    Run the command to check the version of Apache Struts installed in your environment
    Affected if The installed version is less than 1.2.9
  2. Inspect multipart/form-data handling
    Review the configuration files or code to see if multipart/form-data handling is enabled
    Affected if Multipart/form-data handling is enabled
  3. Verify usage of getMultipartRequestHandler
    Search the codebase for references to the getMultipartRequestHandler method
    Affected if The method getMultipartRequestHandler is referenced in the application code

You are affected if you are using Apache Struts version less than 1.2.9 with multipart/form-data handling enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.2.9 or later
Fixed in 1.2.9
Vendor patch struts.apache.org →
Interim mitigation

To remediate this vulnerability, upgrade to Apache Struts version 1.2.9 or later. Additionally, review and sanitize input parameters in multipart/form-data requests to prevent exploitation.

Recommended fix High confidence

Struts 1.2.9 or later

  1. 1. Identify the current Apache Struts version in use by checking project dependencies or library files.
  2. 2. Download Apache Struts version 1.2.9 or later from the official Apache Struts repository (archive.apache.org or struts.apache.org).
  3. 3. Replace the struts-core-*.jar file in your application's WEB-INF/lib directory with the new version.
  4. 4. Update any build configuration files (pom.xml, build.gradle, etc.) to reference Struts 1.2.9 or newer.
  5. 5. Rebuild and redeploy the application.
  6. 6. Verify the application functions correctly and test the multipart form functionality.
Caveat Review migration notes between your current version and 1.2.9 for any deprecated API changes or configuration adjustments required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Struts Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-1547 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-1547 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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