CVE-2022-37598

Exp

Prototype pollution vulnerability in function DEFNODE in ast.js in mishoo UglifyJS 3.13.2 via the name variable in ast.js. NOTE: the vendor considers this an invalid report.

Published: 2022-10-20 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-37598 is rated High Exploit Risk (79.8/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.80%). 2 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2022-37598

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-37598

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-01-23 0.89% 0.80% -0.10%
2 2025-12-20 0.79% 0.89% +0.10%
3 2025-11-21 — 0.79% —

Full EPSS history (19 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-37598

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2022-37598

OS Trackers for CVE-2022-37598

vendor priority summary link
debian unimportant CVE-2022-37598 unimportant priority: Debian including 2 source packages (uglify-js, uglifyjs), 8 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 8. https://security-tracker.debian.org/tracker/CVE-2022-37598
redhat medium — https://access.redhat.com/security/cve/CVE-2022-37598
ubuntu medium CVE-2022-37598 medium priority: Ubuntu including 1 source packages (uglifyjs), 10 status rows across 10 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, trusty, upstream, xenial): not-affected 5, ignored 4, needs-triage 1. https://ubuntu.com/security/CVE-2022-37598

Affected software / configurations for CVE-2022-37598

Vendor Product Version Raw CPE
uglifyjs_project uglifyjs 3.13.2 cpe:2.3:a:uglifyjs_project:uglifyjs:3.13.2:*:*:*:*:node.js:*:*

References for CVE-2022-37598

cvelogic Threat Intelligence