xmldom: Quadratic-memory consumption
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.1.5 through 0.6.0, appendElement in lib/sax.js uses _copy to clone the complete currentNSMap for each nested element that declares a new namespace prefix. Keeping every ancestor map live on the parse stack creates quadratic peak namespace-map storage, so a small highly compressible XML document can exhaust the process heap before application validation. 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
In affected xmldom packages, parsing XML with deeply nested namespace declarations can cause quadratic memory use. A crafted, highly compressible XML document can exhaust the process heap before application validation if the application parses it. The input does not specify whether network access, authentication, or user interaction is required.
Engineers running npm @xmldom/xmldom versions >=0.7.0 <0.8.15 or >=0.9.0 <0.9.12, or npm xmldom versions >=0.1.5 <=0.6.0, should check their applications.