How severe is CVE-2015-6524?

No CVSS score has been assigned to CVE-2015-6524 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-6524?

CVE-2015-6524 affects the following packages: org.apache.activemq:activemq-broker (Maven), org.apache.activemq:activemq-jaas (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-6524?

Update org.apache.activemq:activemq-broker to 5.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-6524 is resolved across your whole dependency graph.

How do I detect CVE-2015-6524 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:activemq-broker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-6524 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2015-6524 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-6524 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-6524?

CVE-2015-6524 has an EPSS (Exploit Prediction Scoring System) score of 8.2%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-6524?

CVE-2015-6524 is classified as CWE-255 (CWE-255). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-6524 published, and has it been updated?

CVE-2015-6524 was published on August 24, 2015 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2015-6524 — activemq-broker

Fix: apache/activemq@22f2f3d

CVE-2015-6524 is a CWE-255 vulnerability in org.apache.activemq:activemq-broker. A fix is available for org.apache.activemq:activemq-broker — see the affected versions and patch details below.

Improper Input Validation in Apache ActiveMQ

Also known asGHSA-23cr-5hr4-rgwv

Published

Aug 24, 2015

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

8.2%probability of exploitation in next 30 days

Lower Risk-0.33%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.apache.activemq:activemq-broker☕org.apache.activemq:activemq-jaas

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:activemq-broker`	≥ 5.0.0&&< 5.10.2	5.10.2`org.apache.activemq:activemq-broker:5.10.2`
☕Maven	`org.apache.activemq:activemq-jaas`	≥ 5.0.0&&< 5.10.2	5.10.2`org.apache.activemq:activemq-jaas:5.10.2`

Affected Products

2 products · 20 configurations

Application

activemqapache

18 versions

5.0.05.1.05.2.05.3.05.3.15.3.25.4.05.4.15.4.25.4.35.5.05.5.1

fedorafedoraproject

2 versions

2223

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:activemq-broker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.activemq:activemq-broker to 5.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-6524 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-6524 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works