Skip to content
Fencer Intel
medium 5.0

CVE-2010-1587 json

Apache ActiveMQ Sensitive Information Disclosure via the Jetty ResourceHandler

published 16y ago modified 4mo ago also GHSA-v2c9-9m8v-8jjm , EUVD-2022-5260

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
78.0%
EPSS 78.0% chance of exploitation in 30 days, percentile 99.5%
public exploits
3
Metasploit and Exploit-DB

Summary

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.

Patch / fix

  • maven org.apache.activemq:activemq-web-console 5.3.2

Is CVE-2010-1587 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-1587 updated

ActiveMQ JSP source disclosure

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-33868)
  2. Published

Exploit prediction

78.02% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.activemq:activemq-web-console
>=5.0.0, <5.3.2
5.3.2

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.