How severe is CVE-2017-1000487?

CVE-2017-1000487 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-1000487?

CVE-2017-1000487 affects the following packages: org.codehaus.plexus:plexus-utils (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-1000487?

Update org.codehaus.plexus:plexus-utils to 3.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000487 is resolved across your whole dependency graph.

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

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

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

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

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

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

CVE-2017-1000487 has an EPSS (Exploit Prediction Scoring System) score of 6.5%, placing it in the 94th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-1000487?

CVE-2017-1000487 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2017-1000487 was published on January 3, 2018 and was last updated on October 20, 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

CRITICAL severity

CVE-2017-1000487 — plexus-utils

CRITICALFix: codehaus-plexus/plexus-utils@b38a1b3

CVE-2017-1000487 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in org.codehaus.plexus:plexus-utils. A fix is available for org.codehaus.plexus:plexus-utils — see the affected versions and patch details below.

OS Command Injection in Plexus-utils

Also known asGHSA-8vhq-qq4p-grq3SNYK-JAVA-ORGCODEHAUSPLEXUS-31522

Published

Jan 3, 2018

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

6.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% 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

1 pkg affected

☕org.codehaus.plexus:plexus-utils

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

Plexus-utils before 3.0.16 is vulnerable to command injection because it does not correctly process the contents of double quoted strings.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.codehaus.plexus:plexus-utils`	all versions	3.0.16`org.codehaus.plexus:plexus-utils:3.0.16`

Affected Products

2 products · 4 configurations

Application

plexus-utilscodehaus-plexus

< 3.0.16

range

debian linuxdebian

3 versions

7.08.09.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.codehaus.plexus:plexus-utils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.codehaus.plexus:plexus-utils to 3.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000487 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This issue affects the versions of plexus-utils as shipped with Red Hat Enterprise Linux 7 as well as Red Hat Satellite 6.0 and 6.1. Red Hat Satellite 6.2 and later do not ship plexus-utils, as such they are not affected by this vulnerability. Red Hat Product Security has rated this issue as having Moderate security…

Product	Fixed in	Advisory
Red Hat JBoss A-MQ 6.3	`plexus-utils`	RHSA-2018:1322

Frequently Asked Questions

Plexus-utils before 3.0.16 is vulnerable to command injection because it does not correctly process the contents of double quoted strings.

O3 Security · Impact-Aware SCA

Is CVE-2017-1000487 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works