CVE-2015-6524: Improper Input Validation in Apache ActiveMQ

Summary

17/05/2022
Yes i
Moderate
Not published

CVE-2015-6524: Improper Input Validation in Apache ActiveMQ. Affects org.apache.activemq:activemq-broker versions >= 5.0.0, < 5.10.2. Fixed in 5.10.2. How to fix ↓

Also tracked for

The same CVE-2015-6524 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

Apache ActiveMQ is an open-source message broker written in Java that provides reliable messaging between distributed applications. It is widely used for building scalable and high-performance messaging systems. The ActiveMQ client library, specifically the 'org.apache.activemq:activemq-client' package, is affected by a vulnerability that allows remote attackers to obtain credentials through a brute force attack.

Vulnerability Detail

The LDAPLoginModule implementation in the Java Authentication and Authorization Service (JAAS) in Apache ActiveMQ 5.x before 5.10.1 allows wildcard operators in usernames. This allows an attacker to perform a brute force attack to obtain valid credentials. By using wildcard operators, the attacker can try multiple combinations of usernames, increasing the chances of success. This vulnerability can lead to unauthorized access to the ActiveMQ message broker and potentially compromise the confidentiality and integrity of the messaging system.

How To Fix

Minimum fixed version

5.10.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to a patched version of Apache ActiveMQ.

Conclusion

The vulnerability in Apache ActiveMQ allows remote attackers to obtain credentials through a brute force attack. To mitigate this risk, it is crucial to upgrade to Apache ActiveMQ version 5.10.2 or later. This will prevent the use of wildcard operators in usernames and protect the messaging system from unauthorized access. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.activemq:activemq-broker →

Share this vulnerability

FAQ

Apache ActiveMQ is an open-source message broker written in Java that provides reliable messaging between distributed applications.

This vulnerability allows remote attackers to obtain credentials through a brute force attack, potentially leading to unauthorized access to the ActiveMQ message broker and compromising the confidentiality and integrity of the messaging system.

To fix this vulnerability, it is recommended to upgrade to Apache ActiveMQ version 5.10.2 or later.

There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to a patched version of Apache ActiveMQ.

You can find more information about this vulnerability in the CVE-2015-6524 entry or by contacting the Apache ActiveMQ community.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.activemq:activemq-broker.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

5.10.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback