CVE-2024-37372

The Permission Model assumes that any path starting with two backslashes \ has a four-character prefix that can be ignored, which is not always true. This subtle bug leads to vulnerable edge cases.

Published: 2025-01-09 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-37372 is rated Low Risk (26.7/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.43%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-37372

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.07% 0.43% +0.36%
2 2026-05-31 0.05% 0.07% +0.02%
3 2026-03-25 — 0.05% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-37372

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.6 3.0 LOW
CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.0 2.5 [email protected]

Weakness enumeration for CVE-2024-37372

OS Trackers for CVE-2024-37372

vendor priority summary link
debian unimportant CVE-2024-37372 unimportant priority: Debian including 1 source packages (nodejs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-37372
gentoo high CVE-2024-37372: 1 GLSA(s) (202505-11), 1 atom(s) (net-libs/nodejs); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2024-37372
redhat low — https://access.redhat.com/security/cve/CVE-2024-37372
ubuntu medium CVE-2024-37372 medium priority: Ubuntu including 1 source packages (nodejs), 10 status rows across 10 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, trusty, upstream, xenial): not-affected 9, ignored 1. https://ubuntu.com/security/CVE-2024-37372

Affected software / configurations for CVE-2024-37372

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-37372

cvelogic Threat Intelligence