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

CVE-2020-28471

CRITICALFix: steveukx/properties@0877cc8

CVE-2020-28471 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in properties-reader. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2020-28471 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Properties-Reader before v2.2.0 vulnerable to prototype pollution

Also known asGHSA-jxvf-m3x5-mxwq
Published
Jul 25, 2022
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known

Real-World Exposure

1 pkg affected

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

properties-readernpm
5.7Mdownloads / week

Description

This affects the package properties-reader before 2.2.0.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmproperties-readerall versions2.2.0
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 properties-reader. 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 properties-reader to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28471 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-2020-28471 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-2020-28471. 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 properties-reader before 2.2.0.
O3 Security · Impact-Aware SCA

Is CVE-2020-28471 in your dependencies?

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