xmldom: XML injection through unvalidated DocumentType serialization
xmldom
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @xmldom/xmldom npm |
|
|
| xmldom npm |
| No fix yet |
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. In @xmldom/xmldom prior to versions 0.9.10 and 0.8.13 and xmldom version 0.6.0 and prior, the package serializes DocumentType node fields (internalSubset, publicId, systemId) verbatim without any escaping or validation. When these fields are set programmatically to attacker-controlled strings, XMLSerializer.serializeToString can produce output where the DOCTYPE declaration is terminated early and arbitrary markup appears outside it. This issue has been patched in versions @xmldom/xmldom versions 0.9.10 and 0.8.13.
From the CVE record · GitHub_M
The affected xmldom packages serialize DocumentType fields without escaping or validation. If an attacker controls values assigned to those fields programmatically, XMLSerializer.serializeToString can terminate the DOCTYPE declaration early and place arbitrary markup outside it. The input does not specify a network, authentication, or user-interaction requirement.
Engineers using npm @xmldom/xmldom versions below 0.8.13 or from 0.9.0 through 0.9.9, or npm xmldom versions through 0.6.0, should check their deployments.