CVE Tools
Track your stack

CVE-2023-32002

No known exploitation. EPSS puts it in the 76th percentile. Fixed versions are out.

CVSS 3.19.8CriticalEPSS percentile76th1.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix5 products4 fixed builds listed below

Published Updated Sources: CVE.org, NVD, BDU, CSAF

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • NodeJS NodeAffected: ≥ 4.0, < 4.*Upgrade to: 4.*Affected: ≥ 5.0, < 5.*Upgrade to: 5.*Affected: ≥ 6.0, < 6.*Upgrade to: 6.*Affected: ≥ 7.0, < 7.*Upgrade to: 7.* + 13 more branchesStated by: CVE record
  • Nodejs Node.jsAffected: ≥ 16.0.0, ≤ 16.20.1Upgrade to: after 16.20.1Stated by: NVD
  • Red Hat Inc. Red Hat Enterprise LinuxAffected: 8Upgrade to: not statedStated by: BDU
  • ООО «Ред Софт» РЕД ОСAffected: 7.3Upgrade to: not statedStated by: BDU
  • Node.js Foundation Node.jsAffected: от 16.0.0 до 16.20.2Upgrade to: not statedStated by: BDU

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS76th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.6% chance of exploitation activity in the next 30 days, which ranks it in the 76th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 1039 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Publishedweakness classified

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

References in the record

And 15 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Node, not every advisory.