How severe is CVE-2017-15709?

CVE-2017-15709 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-15709?

CVE-2017-15709 affects the following packages: org.apache.activemq:activemq-openwire-generator (Maven), org.apache.activemq:activemq-parent (Maven), org.apache.activemq:activemq-parent (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-15709?

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

How do I detect CVE-2017-15709 in my Maven dependencies?

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2017-15709 actively exploited in the wild?

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

CVE-2017-15709 has an EPSS (Exploit Prediction Scoring System) score of 22.8%, placing it in the 98th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2017-15709?

CVE-2017-15709 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-15709 published, and has it been updated?

CVE-2017-15709 was published on February 13, 2018 and was last updated on October 24, 2026. 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

LOW severity

CVE-2017-15709 — activemq-openwire-generat…

LOWFix: apache/activemq@8ff18c5

CVE-2017-15709 is a low-severity (CVSS 3.7) Information Exposure vulnerability in org.apache.activemq:activemq-openwire-generator. EPSS puts its 30-day exploitation probability at 22.8% (98th percentile). A fix is available for org.apache.activemq:activemq-openwire-generator — see the affected versions and patch details below.

ActiveMQ's OpenWire protocol exposes certain system details as plain text

Also known asGHSA-7qm4-p377-fr2r

Published

Feb 13, 2018

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

22.8%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.apache.activemq:activemq-openwire-generator☕org.apache.activemq:activemq-parent☕org.apache.activemq:activemq-parent

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

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:activemq-openwire-generator`	≥ 5.14.0&&< 5.15.3	5.15.3`org.apache.activemq:activemq-openwire-generator:5.15.3`
☕Maven	`org.apache.activemq:activemq-parent`	≥ 5.15.0&&< 5.15.3	5.15.3`org.apache.activemq:activemq-parent:5.15.3`
☕Maven	`org.apache.activemq:activemq-parent`	≥ 5.14.0&&< 5.14.6	5.14.6`org.apache.activemq:activemq-parent:5.14.6`

Affected Products

1 product · 1 configurations

Application

activemqapache

≥ 5.14.0 && ≤ 5.15.2

range

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-openwire-generator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.activemq:activemq-openwire-generator to 5.15.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-15709 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2017-15709 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works