dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2011-4605

HIGH · 7.5 CVSS v2.0 Published 2012-11-23
Fix available
A fix is available. Upgrade to after 5.2.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The (1) JNDI service, (2) HA-JNDI service, and (3) HAJNDIFactory invoker servlet in JBoss Enterprise Application Platform 4.3.0 CP10 and 5.1.2, Web Platform 5.1.2, SOA Platform 4.2.0.CP05 and 4.3.0.CP05, Portal Platform 4.3 CP07 and 5.2.x before 5.2.2, and BRMS Platform before 5.3.0 do not properly restrict write access, which allows remote attackers to add, delete, or modify items in a JNDI tree via unspecified vectors.

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

This is an improper access control vulnerability in JBoss Enterprise products where the JNDI, HA-JNDI, and HAJNDIFactory invoker servlets fail to restrict write access to the JNDI tree. Remote attackers can add, delete, or modify items in the JNDI namespace without authentication.

MitigationApply vendor patches for the affected JBoss platforms (4.3.0 CP10, 5.1.2, 5.2.x); if patches are unavailable, disable the vulnerable JNDI invoker servlets or restrict network access to these endpoints.

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
Jboss Enterprise Application PlatformApplication
Affected:= 4.3.0= 5.1.2
Jboss Enterprise Brms PlatformApplication
Affected:<= 5.2.0
Jboss Enterprise Portal PlatformApplication
Affected:= 4.3.0= 5.2.0= 5.2.1
Jboss Enterprise Soa PlatformApplication
Affected:= 4.2.0= 4.3.0
Jboss Enterprise Web PlatformApplication
Affected:= 5.1.2

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

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. Identify JBoss installation directory
    Locate the JBOSS_HOME environment variable or check common installation paths such as /opt/jboss, /usr/share/jboss, or C:\jboss. Look for the bin/run.sh or bin/run.bat script.
    Affected if Unable to locate JBoss installation indicates it may not be present or may be in a non-standard location.
  2. Determine JBoss version
    Check the JBoss version by inspecting the manifest in $JBOSS_HOME/lib/jboss.jar, or look for a version.txt file in the installation root, or grep the startup logs for the version string.
    Affected if Running version 4.3.0, 5.1.2, or any 4.2.x, 4.3.x, 5.0.x, 5.1.x, or 5.2.x version falls within the affected range listed in the CVE.
  3. Check for deployed JNDI invoker servlets
    Search the deploy directory (e.g., $JBOSS_HOME/server/default/deploy/ or $JBOSS_HOME/server/all/deploy/) for files containing 'invoker' in the name, specifically jboss-net.sar, http-invoker.sar, or any WAR containing JNDI, HA-JNDI, or HAJNDIFactory servlets.
    Affected if If these invoker servlet archives exist in the deploy folder, the vulnerable component is present.
  4. Verify invoker servlet configuration
    Inspect the WEB-INF/web.xml file inside the invoker WAR (such as jboss-net.sar or http-invoker.sar) and look for servlet definitions of JNDI, HA-JNDI, or HAJNDIFactory.
    Affected if Presence of these servlet definitions indicates the vulnerable JNDI write access feature is enabled.
  5. Check servlet URL mappings
    Examine the same web.xml to identify the URL patterns these servlets are mapped to (typically /JNDIInvoker or /HAJNDIInvoker), confirming they are accessible over HTTP.
    Affected if The servlets are exposed via accessible URL mappings, making the flaw exploitable over the network.

You are affected if your JBoss installation matches one of the listed affected versions AND the JNDI invoker servlets are deployed and accessible, allowing unauthenticated write access to the JNDI tree.

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.

From vendor data
Upgrade available Upgrade to a release after 5.2.0
Interim mitigation

Apply vendor patches for the affected JBoss platforms (4.3.0 CP10, 5.1.2, 5.2.x); if patches are unavailable, disable the vulnerable JNDI invoker servlets or restrict network access to these endpoints.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-4605 — 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 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-2011-4605 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