Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

GHSA-wpg7-2c88-r8xv

HIGHFix: feross/simple-get#75

GHSA-wpg7-2c88-r8xv is a high-severity (CVSS 7.5) CWE-212 vulnerability in simple-get. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-wpg7-2c88-r8xv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Exposure of Sensitive Information in simple-get

Also known asCVE-2022-0355
Published
Jan 28, 2022
Updated
Nov 8, 2023
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

simple-getnpm
26.3Mdownloads / week

Description

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

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
📦npmsimple-get4.0.0&&< 4.0.14.0.1
📦npmsimple-get3.0.0&&< 3.1.13.1.1
📦npmsimple-getall versions2.8.2
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 simple-get. 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 simple-get to 4.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wpg7-2c88-r8xv 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 GHSA-wpg7-2c88-r8xv 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 GHSA-wpg7-2c88-r8xv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-wpg7-2c88-r8xv in your dependencies?

O3 detects GHSA-wpg7-2c88-r8xv across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-wpg7-2c88-r8xv: Exposure of Sensitive… | O3 Security