How severe is CVE-2010-1587?

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

Which packages are affected by CVE-2010-1587?

CVE-2010-1587 affects the following packages: org.apache.activemq:activemq-web-console (Maven). Ecosystems affected: Maven.

How do I fix CVE-2010-1587?

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

How do I detect CVE-2010-1587 in my Maven dependencies?

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

How do I mitigate CVE-2010-1587 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-2010-1587 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2010-1587, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2010-1587?

CVE-2010-1587 has an EPSS (Exploit Prediction Scoring System) score of 78.0%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2010-1587?

CVE-2010-1587 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2010-1587?

A Metasploit module references CVE-2010-1587, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2010-1587 published, and has it been updated?

CVE-2010-1587 was published on May 14, 2022 and was last updated on December 4, 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-2010-1587 — activemq-web-console

Fix: apache/activemq@aadd17a

CVE-2010-1587 is a Improper Input Validation vulnerability in org.apache.activemq:activemq-web-console. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.activemq:activemq-web-console — see the affected versions and patch details below.

Apache ActiveMQ Sensitive Information Disclosure via the Jetty ResourceHandler

Published

May 14, 2022

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

78.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.apache.activemq:activemq-web-console

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 Jetty ResourceHandler in Apache ActiveMQ 5.x before 5.3.2 and 5.4.x before 5.4.0 allows remote attackers to read JSP source code via a // (slash slash) initial substring in a URI for (1) admin/index.jsp, (2) admin/queues.jsp, or (3) admin/topics.jsp.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:activemq-web-console`	≥ 5.0.0&&< 5.3.2	5.3.2`org.apache.activemq:activemq-web-console:5.3.2`

Affected Products

1 product · 6 configurations

Application

activemqapache

6 versions

5.0.05.1.05.2.05.3.05.3.15.4-snapshot

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-33868remotemultiple✓ Verified

Apache ActiveMQ 5.2/5.3 - Source Code Information Disclosure

by Veerendra G.G · Apr 22, 2010

Exploit-DB Source

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-web-console, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.activemq:activemq-web-console to 5.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-1587 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-2010-1587 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works