# CVE-2017-15709: ActiveMQ's OpenWire protocol exposes certain system details as plain text

> Attackers can obtain sensitive system details like OS and kernel versions via the OpenWire protocol in Apache ActiveMQ.

- **Severity:** Low 3.7 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-15709, GHSA-7qm4-p377-fr2r

## What is CVE-2017-15709?

CVE-2017-15709 is a low-severity vulnerability in Apache Activemq, published on 13 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When using the OpenWire protocol in ActiveMQ versions 5.14.0 to 5.15.2 it was found that certain system details (such as the OS and kernel version) are exposed as plain text.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-15709?

6 open source packages ship an affected version, including org.apache.activemq:activemq-parent and org.apache.activemq:activemq-openwire-generator. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.activemq:activemq-parent` | Maven | From 5.14.0 | 5.14.6 |
| `org.apache.activemq:activemq-parent` | Maven | From 5.14.0 | 5.14.6 |
| `org.apache.activemq:activemq-parent` | Maven | From 5.15.0 | 5.15.3 |
| `org.apache.activemq:activemq-parent` | Maven | From 5.15.0 | 5.15.3 |
| `org.apache.activemq:activemq-openwire-generator` | Maven | From 5.14.0 | 5.15.3 |
| `org.apache.activemq:activemq-openwire-generator` | Maven | From 5.14.0 | 5.15.3 |

Products: Apache Activemq.

## How do I fix CVE-2017-15709?

Upgrade org.apache.activemq:activemq-parent to a fixed version for your release line: 5.14.6 or 5.15.3.

## Is CVE-2017-15709 being exploited?

There is no known exploitation of CVE-2017-15709 in the wild and no public exploit code.

## Other vulnerabilities in Apache Activemq

- [CVE-2023-46604](https://insights.sbomify.com/CVE-2023-46604/): Apache ActiveMQ Deserialization of Untrusted Data (critical 10.0, exploited in the wild)
- [CVE-2016-3088](https://insights.sbomify.com/CVE-2016-3088/): Apache ActiveMQ Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2026-34197](https://insights.sbomify.com/CVE-2026-34197/): Apache ActiveMQ Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2020-11998](https://insights.sbomify.com/CVE-2020-11998/): Remote code execution in Apache ActiveMQ (critical 9.8)
- [CVE-2013-7285](https://insights.sbomify.com/CVE-2013-7285/): Command Injection in Xstream (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15709 and fix it if it is affected.

What it is: CVE-2017-15709 is a low-severity vulnerability in Apache Activemq, published on 13 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15709 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.activemq:activemq-parent (Maven): affected from 5.14.0; fixed in 5.14.6
- org.apache.activemq:activemq-parent (Maven): affected from 5.14.0; fixed in 5.14.6
- org.apache.activemq:activemq-parent (Maven): affected from 5.15.0; fixed in 5.15.3
- org.apache.activemq:activemq-parent (Maven): affected from 5.15.0; fixed in 5.15.3
- org.apache.activemq:activemq-openwire-generator (Maven): affected from 5.14.0; fixed in 5.15.3
- org.apache.activemq:activemq-openwire-generator (Maven): affected from 5.14.0; fixed in 5.15.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-15709/ (Markdown: https://insights.sbomify.com/CVE-2017-15709/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-15709
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-15709
- OSV: https://osv.dev/vulnerability/CVE-2017-15709

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-15709/
Summaries are generated and may contain mistakes; the official description above is the record.