xmldom up to 0.8.2 dom.js prototype pollution

Summaryinfo

A vulnerability was found in xmldom up to 0.8.2. It has been rated as problematic. Impacted is an unknown function of the file dom.js. The manipulation of the argument p leads to prototype pollution. This vulnerability is listed as CVE-2022-37616. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in xmldom up to 0.8.2. This issue affects an unknown function of the file dom.js. The manipulation of the argument p with an unknown input leads to a prototype pollution vulnerability. Using CWE to declare the problem leads to CWE-1321. The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was presented 10/11/2022 as 436. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-37616 since 08/08/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.

Upgrading to version 0.8.3 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• xmldom

Version

• 0.8.0
• 0.8.1
• 0.8.2

Website

• Product: https://github.com/xmldom/xmldom/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion