xmldom: Attribute name injection via setAttribute() bypasses requireWellFormed
xmldom · @xmldom xmldom
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @xmldom/xmldom npm |
|
|
| xmldom npm |
| No fix yet |
xmldom · @xmldom xmldom
| Product | Affected | Fixed in |
|---|---|---|
| @xmldom/xmldom npm |
|
|
| xmldom npm |
| No fix yet |
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.14 and 0.9.11, and in xmldom version 0.6.0 and earlier, Element.setAttribute() calls the private _createAttribute(name) path without validating the attribute name, while Document.createAttribute(name) validates against QName. XMLSerializer.serializeToString() emits attribute names verbatim, and requireWellFormed: true did not validate them, so a crafted name can terminate the intended attribute and inject additional attributes, including event handlers, into browser-consumed output; synthesized xmlns:PREFIX declarations expose the same unchecked-name boundary. This issue is fixed in @xmldom/xmldom versions 0.8.14 and 0.9.11; no fixed version is available for xmldom.
From the CVE record · GitHub_M
Affected xmldom packages do not validate attribute names passed through Element.setAttribute(), even when serialization uses requireWellFormed: true. If an attacker can supply a crafted attribute name and the serialized output is consumed by a browser, they can inject additional attributes, including event handlers. The input does not specify whether authentication or user interaction is required.
Check applications using npm @xmldom/xmldom versions >=0.9.0 <0.9.11 or >=0.7.0 <0.8.14, or npm xmldom version 0.6.0 or earlier.