# Apache ActiveMQ Sensitive Information Disclosure via the Jetty ResourceHandler

Advisory record · `GHSA-v2c9-9m8v-8jjm`

- **Identifiers:** `GHSA-v2c9-9m8v-8jjm` · `CVE-2010-1587`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html)
- **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 14 May 2022
- **Updated:** 4 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2022, 02:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.activemq:activemq-web-console` (Maven): affected `>=5.0.0, <5.3.2`; fixed in `5.3.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The activemq-web-console package in Apache ActiveMQ versions 5.0.0 before 5.3.2 is affected. A remote attacker can use a URI beginning with a double slash to read the JSP source code of the admin index, queues, and topics pages. Upgrade to version 5.3.2.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.78, the 99th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-v2c9-9m8v-8jjm)

## Sources

- [GitHub Advisory Database: GHSA-v2c9-9m8v-8jjm](https://github.com/advisories/GHSA-v2c9-9m8v-8jjm)
- [OSV: GHSA-v2c9-9m8v-8jjm](https://osv.dev/vulnerability/GHSA-v2c9-9m8v-8jjm)
- <https://nvd.nist.gov/vuln/detail/CVE-2010-1587>
- <https://github.com/apache/activemq/commit/aadd17ab7b6b6a664322538d25ee96dad67616e0>
- <https://github.com/apache/activemq>
- <https://github.com/apache/activemq/compare/activemq-5.3.1...activemq-parent-5.3.2>
- <https://github.com/apache/activemq/tree/main/activemq-web-console/src/main/webapp>
- <https://issues.apache.org/activemq/browse/AMQ-2700>
- <https://web.archive.org/web/20100426064914/http://www.vupen.com/english/advisories/2010/0979>
- <https://web.archive.org/web/20100702082040/http://secunia.com/advisories/39567>
- <https://web.archive.org/web/20150314050810/http://archives.neohapsis.com/archives/fulldisclosure/2010-04/0278.html>
- <https://web.archive.org/web/20200228044456/http://www.securityfocus.com/bid/39636>
- <https://web.archive.org/web/20201208002259/http://www.securityfocus.com/archive/1/510896/100/0/threaded>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-v2c9-9m8v-8jjm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-v2c9-9m8v-8jjm/>. Everything for agents: <https://agentprime.io/llms.txt>.
