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

GHSA-6fw4-hr69-g3rv

CRITICALFix: jquense/expr@df84691

GHSA-6fw4-hr69-g3rv is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in property-expr. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-6fw4-hr69-g3rv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in property-expr

Also known asCVE-2020-7707
Published
May 6, 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

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.

66other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
property-exprnpm
11.3Mdownloads / week

Description

The package property-expr before 2.0.3 are vulnerable to Prototype Pollution via the setter function.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmproperty-exprall versions2.0.3
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 property-expr. 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 property-expr to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fw4-hr69-g3rv 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-6fw4-hr69-g3rv 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-6fw4-hr69-g3rv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The package property-expr before 2.0.3 are vulnerable to Prototype Pollution via the setter function.
O3 Security · Impact-Aware SCA

Is GHSA-6fw4-hr69-g3rv in your dependencies?

O3 detects GHSA-6fw4-hr69-g3rv 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-6fw4-hr69-g3rv: Prototype Pollution in… | O3 Security