Summary
Improper Authentication in Apache WSS4J
The LDAPLoginModule implementation in the Java Authentication and Authorization Service (JAAS) in Apache ActiveMQ 5.x before 5.10.1 allows remote attackers to bypass authentication by logging in with an empty password and valid username, which triggers an unauthenticated bind. NOTE: this identifier has been SPLIT per ADT2 due to different vulnerability types. See CVE-2015-6524 for the use of wildcard operators in usernames.
Impact
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.apache.activemq:activemq-broker to 5.10.1 or later; org.apache.activemq:activemq-jaas to 5.10.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2014-3612? CVE-2014-3612 is a high-severity improper authentication vulnerability in org.apache.activemq:activemq-broker (maven), affecting versions >= 5.0.0, < 5.10.1. It is fixed in 5.10.1. The application does not adequately verify the identity of a user, device, or process before granting access.
- Which packages are affected by CVE-2014-3612?
org.apache.activemq:activemq-broker(maven) (versions >= 5.0.0, < 5.10.1)org.apache.activemq:activemq-jaas(maven) (versions >= 5.0.0, < 5.10.1)
- Is there a fix for CVE-2014-3612? Yes. CVE-2014-3612 is fixed in 5.10.1. Upgrade to this version or later.
- Is CVE-2014-3612 exploitable, and should I be worried? Whether CVE-2014-3612 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2014-3612 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2014-3612?
- Upgrade
org.apache.activemq:activemq-brokerto 5.10.1 or later - Upgrade
org.apache.activemq:activemq-jaasto 5.10.1 or later
- Upgrade