xmldom: XML node injection through unvalidated processing instruction 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 allows attacker-controlled processing instruction data to be serialized into XML without validating or neutralizing the PI-closing sequence ?>. As a result, an attacker can terminate the processing instruction early and inject arbitrary XML nodes into the serialized output. This issue has been patched in versions @xmldom/xmldom versions 0.9.10 and 0.8.13.
From the CVE record · GitHub_M
The XML serializer in affected xmldom packages does not validate or neutralize the processing-instruction closing sequence `?>`. If an attacker controls processing-instruction data being serialized, they can end the instruction early and inject arbitrary XML nodes into the output. The input does not specify whether authentication, network access, or user interaction is required.
Check applications using npm @xmldom/xmldom versions below 0.8.13 or from 0.9.0 to below 0.9.10, or npm xmldom version 0.6.0 or earlier.