Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

CVE-2017-1000220

CRITICAL

CVE-2017-1000220 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in pidusage. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2017-1000220 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

PIDUsage Enables OS Command Injection

Also known asGHSA-h2p3-h48h-9jj7
Published
Nov 17, 2017
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

pidusagenpm
4.0Mdownloads / week

Description

soyuka/pidusage <=1.1.4 is vulnerable to command injection in the module resulting in arbitrary command execution

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmpidusageall versions1.1.5
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pidusage. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update pidusage to 1.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000220 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2017-1000220 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2017-1000220. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

soyuka/pidusage <=1.1.4 is vulnerable to command injection in the module resulting in arbitrary command execution
O3 Security · Impact-Aware SCA

Is CVE-2017-1000220 in your dependencies?

O3 detects CVE-2017-1000220 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.