How severe is CVE-2014-3612?

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

Which packages are affected by CVE-2014-3612?

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

How do I fix CVE-2014-3612?

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

How do I detect CVE-2014-3612 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-2014-3612 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2014-3612 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-3612 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-2014-3612?

CVE-2014-3612 has an EPSS (Exploit Prediction Scoring System) score of 6.9%, placing it in the 94th 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-2014-3612?

CVE-2014-3612 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-3612 published, and has it been updated?

CVE-2014-3612 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.

CVE-2014-3612: activemq-broker

EPSS Exploitation Probability

via FIRST.org ↗

6.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% 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 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.

Affected Packages

2 total 2 fixed

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

Affected Products

1 product · 18 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

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.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3612 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

RHSA-2015:0138Fuse ESB Enterprise 7.1.0 RHSA-2015:0137Red Hat JBoss A-MQ 6.1

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2014-3612 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2014-3612 — activemq-broker