Withdrawn: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in @xmldom/xmldom and xmldom
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @xmldom/xmldom npm |
|
|
| xmldom npm |
|
| Product | Affected | Fixed in |
|---|---|---|
| @xmldom/xmldom npm |
|
|
| xmldom npm |
|
| No fix yet |
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."
From the CVE record · mitre
The copy function in dom.js has a reported prototype pollution vulnerability involving the p variable. The report is disputed by the vendor, which says it is in the process of marking it invalid. The input does not specify attack access, authentication requirements, or user interaction.
Check applications using npm @xmldom/xmldom versions <0.7.6, >=0.8.0 <0.8.3, or >=0.9.0-beta.1 <0.9.0-beta.2, and npm xmldom versions <=0.6.0.