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

GHSA-v39p-96qg-c8rf

MEDIUMFix: mariocasciaro/object-path@7bdf4ab

GHSA-v39p-96qg-c8rf is a medium-severity (CVSS 5.6) CWE-843 vulnerability in object-path. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-v39p-96qg-c8rf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in object-path

Also known asCVE-2021-23434
Published
Sep 1, 2021
Updated
Jan 14, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Jan 14, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦object-path

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

This affects the package object-path before 0.11.6. A type confusion vulnerability can lead to a bypass of CVE-2020-15256 when the path components used in the path parameter are arrays. In particular, the condition currentPath === '__proto__' returns false if currentPath is ['__proto__']. This is because the === operator returns always false when the type of the operands is different.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmobject-pathall versions0.11.6
Exploits & PoCs
2

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 object-path. 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 object-path to 0.11.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v39p-96qg-c8rf 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-v39p-96qg-c8rf 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-v39p-96qg-c8rf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This affects the package object-path before 0.11.6. A type confusion vulnerability can lead to a bypass of CVE-2020-15256 when the path components used in the path parameter are arrays. In particular, the condition `currentPath === '__proto__'` returns false if `currentPath` is `['__proto__']`. This is because the `===` operator returns always false when the type of the operands is different.
O3 Security · Impact-Aware SCA

Is GHSA-v39p-96qg-c8rf in your dependencies?

O3 detects GHSA-v39p-96qg-c8rf 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-v39p-96qg-c8rf: Prototype Pollution in… | O3 Security