Commons BeanutilsApplication · Apache

CVE-2014-0114

HIGH · 7.5 CVSS v2.0 Published 2014-04-30

Fix available

A fix is available. Upgrade to after 1.9.1 or later.

See remediation →

84/100

Remediation priority · High

High EPSS Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Apache Commons BeanUtils, as distributed in lib/commons-beanutils-1.8.0.jar in Apache Struts 1.x through 1.3.10 and in other products requiring commons-beanutils through 1.9.2, does not suppress the class property, which allows remote attackers to "manipulate" the ClassLoader and execute arbitrary code via the class parameter, as demonstrated by the passing of this parameter to the getClass method of the ActionForm object in Struts 1.

Technical summary

dbcve analysis · high confidence

Apache Commons BeanUtils fails to suppress the 'class' property during bean introspection, allowing remote attackers to access the ClassLoader through the class parameter and execute arbitrary code via the getClass method. This affects Struts 1.x (1.0-1.3.10) and any other Java applications using commons-beanutils through 1.9.2.

MitigationUpgrade Apache Commons BeanUtils to version 1.9.3 or later which properly suppresses the class property. For legacy Struts 1 applications, consider migrating to Struts 2.x or implement input filtering to block the class parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Commons BeanutilsApplication

Affected:<= 1.9.1

StrutsFramework / library

Affected:= 1.0= 1.0.2= 1.1= 1.2.2= 1.2.4= 1.2.6= 1.2.7= 1.2.8= 1.2.9= 1.3.5= 1.3.8= 1.3.10

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected?

dbcve checks

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

Locate Apache Commons BeanUtils JAR file

Search for commons-beanutils*.jar in your application dependencies (lib directory, Maven pom.xml, or application WAR file)

Affected if The commons-beanutils JAR version is 1.9.1 or earlier (1.9.0, 1.8.3, etc.)
Check Apache Commons BeanUtils version

Open the JAR MANIFEST.MF file or examine the pom.xml dependency declaration to identify the exact version number

Affected if The declared version is 1.9.1 or any version below 1.9.2
Locate Apache Struts 1.x library files

Search for struts-core*.jar or struts*.jar files in your application deployment and identify the Struts 1.x version from the filename or manifest

Affected if Struts 1.0 through 1.3.10 is present (including 1.3.10, 1.3.8, 1.3.5, 1.2.9, etc.)
Verify if application uses BeanUtils for bean introspection

Review application code for imports of org.apache.commons.beanutils.BeanUtils or PropertyUtils and check if request parameters are passed to these utilities

Affected if The application directly uses BeanUtils.getProperty() or similar methods with user-supplied input without filtering the 'class' parameter
Check for exposed input vectors

Examine action forms or parameters that accept arbitrary property names and are processed through bean introspection utilities

Affected if The application allows direct or indirect access to bean properties through URL parameters that could include the 'class' parameter

Your environment is affected if you have Apache Commons BeanUtils version 1.9.1 or earlier, or any version of Apache Struts 1.0 through 1.3.10, and your application exposes bean introspection via request parameters without filtering the 'class' property.

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

Remediation

From vendor data

Upgrade available Upgrade to a release after 1.9.1

Interim mitigation

Upgrade Apache Commons BeanUtils to version 1.9.3 or later which properly suppresses the class property. For legacy Struts 1 applications, consider migrating to Struts 2.x or implement input filtering to block the class parameter.

Fix this in Commons Beanutils Scoped from the published advisory

Consultation8.0 h
Implementation16.0 h
Testing24.0 h
Review / QA8.0 h

56.0 hours of engineering $9,520

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2014-0114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2014-0114?

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.

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

At a glance

A fix existsUpgrade to after 1.9.1 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 96.1%

Affects: Commons Beanutils

Remediation

A high-priority fix

Fix this in Commons Beanutils 56 hrs · High

Typical engagement from $9,520

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2014-0114 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References