xmldom: Parser silently accepts a not-well-formed end tag whose name is followed by a line break and trailing content
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, DOMParser.parseFromString() can silently accept an end tag such as </a\njunk>, close the element, and discard the trailing content. On 0.9.x, the lib/sax.js end-tag validator inherits the multiline flag from reg(), allowing the first line to satisfy the anchored XML ETag production; older lines have no equivalent residue validation. This parser differential can bypass a parse-before-trust well-formedness gate, although it does not inject the discarded content; onError on 0.9.x and errorHandler on 0.8.x are the relevant reporting interfaces. 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
DOMParser.parseFromString() can silently accept a malformed XML end tag and discard its trailing content. An attacker supplying XML to an application that relies on parsing to check well-formedness could bypass that check; the discarded content is not injected.
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.