xmldom: Quadratic-time parsing via the malformed-input recovery path — `parseElementStartPart` re-scan and `normalize()` adjacent-text merge
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 versions 0.3.0 through 0.6.0, two independent quadratic paths can cause denial of service. In lib/sax.js, parseElementStartPart repeatedly rescans a malformed tag name to the next > during single-character recovery; in lib/dom.js, normalize() repeatedly removes and appends adjacent text nodes, causing quadratic reindexing and string rebuilding. The first path is reachable through default DOMParser.parseFromString() processing, while the second is also reachable through a direct normalize() call on a programmatically constructed DOM, and endDocument invokes that normalization after parsing. 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
Quadratic processing in XML parsing and DOM normalization can cause denial of service. An attacker can trigger it if an application parses attacker-controlled malformed XML; normalization of a constructed DOM can also trigger it. Network access, authentication requirements, and user interaction depend on how the application exposes these operations.
Check applications using npm @xmldom/xmldom versions >=0.7.0 <0.8.15 or >=0.9.0 <0.9.12, or npm xmldom versions >=0.3.0 <=0.6.0.