Is CVE-2022-37616 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2022-37616 being exploited in the wild.

How severe is CVE-2022-37616?

Low severity, with a CVSS score of 3.1, published 11 October 2022.

Which products and versions are affected?

@xmldom/xmldom (npm) SEMVER:introduced=0.8.0,fixed=0.8.3; xmldom (npm) SEMVER:introduced=0,last_affected=0.6.0.

Is there a fix for CVE-2022-37616?

Yes. @xmldom/xmldom (npm): upgrade to 0.8.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2022-37616 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2022-37616?

Check whether you run @xmldom/xmldom (npm) or xmldom (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2022-37616: xmldom Prototype pollution in copy function

CVE-2022-37616 · Severity: low · CVSS 3.1 · Published 2022-10-11

xmldom is a JavaScript library for parsing and manipulating XML documents, commonly used in Node.js applications. A prototype pollution vulnerability in the copy function could allow attackers to modify core object properties, potentially affecting application behavior or security. However, this advisory has been withdrawn because maintainers and security researchers were unable to create a working exploit or validate the vulnerability's practical impact.

Technologies: @xmldom/xmldom (npm), xmldom (npm). Vendors: npm.

Quick answers

Is CVE-2022-37616 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2022-37616 being exploited in the wild.
How severe is CVE-2022-37616?: Low severity, with a CVSS score of 3.1, published 11 October 2022.
Which products and versions are affected?: @xmldom/xmldom (npm) SEMVER:introduced=0.8.0,fixed=0.8.3; xmldom (npm) SEMVER:introduced=0,last_affected=0.6.0.
Is there a fix for CVE-2022-37616?: Yes. @xmldom/xmldom (npm): upgrade to 0.8.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2022-37616 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2022-37616?: Check whether you run @xmldom/xmldom (npm) or xmldom (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@xmldom/xmldom (npm): upgrade to 0.8.3 or later
```
npm install @xmldom/xmldom@0.8.3
```

Technical details

A prototype pollution vulnerability was reported in the copy function of dom.js in the xmldom library (published as @xmldom/xmldom). The vulnerability, classified as CWE-1321, relates to improper control of object prototype attribute modification. However, the advisory was withdrawn on 2022-11-08 after the package maintainers and multiple third parties disputed the validity of the issue. Attempts to create or replicate a proof-of-concept were unsuccessful, and the original report is being marked as invalid. Patches were released for versions 0.7.6, 0.8.3, and 0.9.0-beta.2, but their necessity remains disputed.

Affected products

xmldom xmldom <=0.6.0
xmldom @xmldom/xmldom <0.7.6, >=0.8.0 <0.8.3, 0.9.0-beta.1

Identifiers

CVE-2022-37616
GHSA-9pgh-qqpf-7wqj

Timeline

2022-10-11: disclosed: Advisory published
2022-11-08: other: Advisory withdrawn; maintainers disputed validity and POC attempts failed

References

https://github.com/xmldom/xmldom/security/advisories/GHSA-9pgh-qqpf-7wqj

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.