dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2012-5629

HIGH · 7.5 CVSS v2.0 Published 2013-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 default configuration of the (1) LdapLoginModule and (2) LdapExtLoginModule modules in JBoss Enterprise Application Platform (EAP) 4.3.0 CP10, 5.2.0, and 6.0.1, and Enterprise Web Platform (EWP) 5.2.0 allow remote attackers to bypass authentication via an empty password.

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

The vulnerability exists in the default configuration of JBoss LDAP login modules (LdapLoginModule and LdapExtLoginModule) which accept empty passwords, allowing remote attackers to bypass authentication by simply supplying an empty password string instead of valid credentials.

MitigationConfigure the LDAP login modules to reject empty passwords by enabling password validation or setting a minimum password length requirement in the module's JAAS configuration.

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.2.0= 6.0.1
Jboss Enterprise Web PlatformApplication
Affected:= 5.2.0

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 and version
    Locate the JBoss installation directory and check the version. On Linux, common paths include /opt/jboss or /usr/share/jboss. Check for version files or examine the manifest in the jbossas-core.jar. On Windows, check Program Files or custom installation paths.
    Affected if The installed version matches Red Hat JBoss Enterprise Application Platform 4.3.0, 5.2.0, or 6.0.1, or JBoss Enterprise Web Platform 5.2.0.
  2. Locate JAAS login configuration files
    Find the JAAS configuration files that define security domains. These are typically named login-config.xml, login-modules.xml, or similar in the conf or server/<profile>/conf directory. Also check for any custom JAAS configuration referenced via JVM arguments.
    Affected if A JAAS configuration file exists and is loaded by the JBoss instance.
  3. Identify LDAP login module usage
    Search the JAAS configuration for entries using LdapLoginModule or LdapExtLoginModule. Look for <login-module> elements with classname containing org.jboss.security.auth.spi.LdapLoginModule or org.jboss.security.auth.spi.LdapExtLoginModule.
    Affected if The configuration contains LdapLoginModule or LdapExtLoginModule in a security domain definition.
  4. Verify empty password validation configuration
    Examine the LDAP login module configuration for parameters that control empty password acceptance. Specifically check for options like password-stacking, hashAlgorithm, or any custom password validation. Look for whether the module is configured to reject empty passwords or enforce minimum password length.
    Affected if No password validation is explicitly configured, or the module is set to allow empty passwords by default (the default behavior without explicit validation).

You are affected if you run a vulnerable JBoss version (EAP 4.3.0, 5.2.0, 6.0.1 or EWP 5.2.0) and have a security domain configured using LdapLoginModule or LdapExtLoginModule without explicit empty password validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure the LDAP login modules to reject empty passwords by enabling password validation or setting a minimum password length requirement in the module's JAAS configuration.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA4.0 h
16.0 hours of engineering $2,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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