cve.bz

CVE-2022-37616 Prototype Pollution

9.8 criticalEPSS 2.1%Fix available

Critical (9.8). EPSS 2.1% estimated probability of exploitation activity in the next 30 days.

On this page
A prototype pollution vulnerability exists in the function copy in dom.js in the xmldom (published as @xmldom/xmldom) package before 0.8.3 for Node.js via the p variable. NOTE: the vendor states "we are in the process of marking this report as invalid"; however, some third parties takes the position that "A prototype injection/Prototype pollution is not just when global objects are polluted with recursive merge or deep cloning but also when a target object is polluted."

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
2.1% (unchanged from 2.1% a week ago; 2.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 82nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-1321 Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-37616 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-37616?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-37616?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-37616 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
xmldom_project:xmldomthrough 0.6.0
xmldom_project:xmldomfrom 0.7.0 before 0.7.6
xmldom_project:xmldomfrom 0.8.0 before 0.8.3
xmldom_project:xmldom0.9.0:beta1
debian:debian_linux10.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian10node-xmldom0.1.27+ds-1+deb10u1DLA-3154-1
Debian12, 13, 14node-xmldom0.8.3-1DEBIAN-CVE-2022-37616
Ubuntu20.04:LTSnode-xmldom0.1.27+ds-1+deb10u2build0.20.04.1UBUNTU-CVE-2022-37616 USN-6102-1
Ubuntu22.04:LTSnode-xmldom0.7.5-1ubuntu0.22.04.1UBUNTU-CVE-2022-37616 USN-6102-1
Azure Linux3python-tensorboard2.16.2-1AZL-38290

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON