Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-6524

activemq: LDAPLoginModule implementation allows wildcard operators in usernames

Overview

Published
24 Aug 2015
Modified
6 May 2026
Medium CVE
2 Registry packages
2 OS packages
3 Linux distributions
Yes Fix available

Description

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, which allows remote attackers to obtain credentials via a brute force attack. NOTE: this identifier was SPLIT from CVE-2014-3612 per ADT2 due to different vulnerability types.

Source: OX vulnerability database

Severity

5 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

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

Weakness: CWE-255

Affected packages · 2

Packages affected by CVE-2015-6524
EcosystemPackageVulnerableFixed in
Maven org.apache.activemq:activemq-broker >=5.0.0, <5.10.2 5.10.2
Maven org.apache.activemq:activemq-jaas >=5.0.0, <5.10.2 5.10.2

Open a package to see all its vulnerabilities.

Operating systems · 7 fixes

debian 3 releases · 1 package

fixed 3
activemq
debian fixes for CVE-2015-6524
ReleasePackageFixed in
11 activemq 5.6.0+dfsg1-4
12 activemq 5.6.0+dfsg1-4
13 activemq 5.6.0+dfsg1-4

echo 1 release · 1 package

fixed 1
activemq
echo fixes for CVE-2015-6524
ReleasePackageFixed in
activemq 5.6.0+dfsg1-4

root.io debian 3 releases · 1 package

fixed 3
rootio-activemq
root.io debian fixes for CVE-2015-6524
ReleasePackageFixed in
11 rootio-activemq 5.6.0+dfsg1-4
12 rootio-activemq 5.6.0+dfsg1-4
13 rootio-activemq 5.6.0+dfsg1-4

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.