CVE-2022-0355 is a high-severity (CVSS 8.8) CWE-212 vulnerability in simple-get. 1 public exploit reference exists, so weaponization risk is real. A fix is available for simple-get — see the affected versions and patch details below.
Improper Removal of Sensitive Information Before Storage or Transfer in feross/simple-get
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-0355 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
simple-getnpmDescription
In versions of simple-get prior to 4.0.1, 3.1.1, and 2.8.2, when fetching a remote url with a cookie location response, headers will be followed, potentially resulting in an exposure of the session cookie to a third party.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | simple-get | ≥ 4.0.0&&< 4.0.1 | 4.0.1npm install simple-get@4.0.1 |
| 📦npm | simple-get | ≥ 3.0.0&&< 3.1.1 | 3.1.1npm install simple-get@3.1.1 |
| 📦npm | simple-get | all versions | 2.8.2npm install simple-get@2.8.2 |
Affected Products
simple-getsimple-get_projectResearch 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 dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simple-get, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update simple-get to 4.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0355 is resolved across your whole dependency graph.
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.
Frequently Asked Questions
Is CVE-2022-0355 in your dependencies?
Find it across npm, including transitive dependencies.