How severe is CVE-2012-6551?

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

Which packages are affected by CVE-2012-6551?

CVE-2012-6551 affects the following packages: org.apache.activemq:apache-activemq (Maven), org.apache.activemq:activemq-web-demo (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-6551?

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

How do I detect CVE-2012-6551 in my Maven dependencies?

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2012-6551 actively exploited in the wild?

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

CVE-2012-6551 has an EPSS (Exploit Prediction Scoring System) score of 7.8%, 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-2012-6551?

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

When was CVE-2012-6551 published, and has it been updated?

CVE-2012-6551 was published on May 17, 2022 and was last updated on December 3, 2024. 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-2012-6551 — apache-activemq

Fix: apache/activemq@22bc55b

CVE-2012-6551 is a CWE-399 vulnerability in org.apache.activemq:apache-activemq. A fix is available for org.apache.activemq:apache-activemq — see the affected versions and patch details below.

Apache ActiveMQ default configuration subject to denial of service

Published

May 17, 2022

Updated

Dec 3, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

7.8%probability of exploitation in next 30 days

Lower Risk0.00%

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:apache-activemq☕org.apache.activemq:activemq-web-demo

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 default configuration of Apache ActiveMQ before 5.8.0 enables a sample web application, which allows remote attackers to cause a denial of service (broker resource consumption) via HTTP requests.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:apache-activemq`	all versions	5.8.0`org.apache.activemq:apache-activemq:5.8.0`
☕Maven	`org.apache.activemq:activemq-web-demo`	all versions	5.8.0`org.apache.activemq:activemq-web-demo:5.8.0`

Affected Products

1 product · 20 configurations

Application

activemqapache

≤ 5.7.0

17 versions

4.04.0.14.0.24.1.04.1.15.0.05.1.05.2.05.3.05.3.15.3.25.4.0

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:apache-activemq, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.activemq:apache-activemq to 5.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-6551 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 HatModerate

RHSA-2013:1029Fuse MQ Enterprise 7.1.0

Frequently Asked Questions

The default configuration of Apache ActiveMQ before 5.8.0 enables a sample web application, which allows remote attackers to cause a denial of service (broker resource consumption) via HTTP requests.

O3 Security · Impact-Aware SCA

Is CVE-2012-6551 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works