CVE-2014-3612

UnknownEPSS 7.38%

Last modified

CVE-2014-3612 is a vulnerability of currently unknown severity. 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. EPSS estimates a 7.38% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
7.38%

93.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
ApacheActivemq5.0.0
ApacheActivemq5.1.0
ApacheActivemq5.2.0
ApacheActivemq5.3.0
ApacheActivemq5.3.1
ApacheActivemq5.3.2
ApacheActivemq5.4.0
ApacheActivemq5.4.1
ApacheActivemq5.4.2
ApacheActivemq5.4.3
ApacheActivemq5.5.0
ApacheActivemq5.5.1
ApacheActivemq5.6.0
ApacheActivemq5.7.0
ApacheActivemq5.8.0
ApacheActivemq5.9.0
ApacheActivemq5.9.1
ApacheActivemq5.10.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2014-3612?
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.
How severe is CVE-2014-3612?
Severity scoring for CVE-2014-3612 is pending analysis. The EPSS model estimates a 7.38% probability of exploitation in the next 30 days.
How do I fix CVE-2014-3612?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2014-3612?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST