xmldom: XML fragment injection via invalid EntityReference.nodeName during requireWellFormed serialization
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.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, Document.createEntityReference(name) accepts an invalid name and the ENTITY_REFERENCE_NODE serializer emits the resulting nodeName directly in &name; form. Directly serializing the node or fragment with XMLSerializer.serializeToString() and requireWellFormed: true can therefore break the entity-reference boundary and produce attacker-controlled XML markup when reparsed. The parser does not ordinarily create these nodes, and element-child insertion is rejected, so exploitation requires an application to create and directly serialize an EntityReference. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
From the CVE record · GitHub_M
Document.createEntityReference(name) accepts invalid names, and direct serialization can emit attacker-controlled XML markup that takes effect when reparsed. Exploitation requires an application to create and directly serialize an EntityReference node or fragment; the parser does not ordinarily create these nodes. The input does not specify network or local access, authentication requirements, or user interaction.
Check applications using @xmldom/xmldom versions >=0.7.0 <0.8.15 or >=0.9.0 <0.9.12, or xmldom version 0.6.0 or earlier.