First published: Tue Jul 27 2021(Updated: )
### Impact xmldom versions 0.6.0 and older do not correctly escape special characters when serializing elements removed from their ancestor. This may lead to unexpected syntactic changes during XML processing in some downstream applications. ### Patches Update to one of the fixed versions of `@xmldom/xmldom` (`>=0.7.0`) See issue #271 for the status of publishing `xmldom` to npm or join #270 for Q&A/discussion until it's resolved. ### Workarounds Downstream applications can validate the input and reject the maliciously crafted documents. ### References Similar to this one reported on the Go standard library: - https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/ - https://mattermost.com/blog/securing-xml-implementations-across-the-web/ ### For more information If you have any questions or comments about this advisory: * Open an issue in [`xmldom/xmldom`](https://github.com/xmldom/xmldom) * Email us: send an email to **all** addresses that are shown by `npm owner ls @xmldom/xmldom`
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
npm/@xmldom/xmldom | <0.7.0 | 0.7.0 |
npm/xmldom | <=0.6.0 | |
xmldom | <0.7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-32796 is considered a medium severity vulnerability due to potential XML processing issues.
To fix CVE-2021-32796, update the xmldom package to version 0.7.0 or higher.
CVE-2021-32796 affects xmldom versions 0.6.0 and older.
The consequences of CVE-2021-32796 may include unexpected syntactic changes during XML processing.
Currently, the recommended approach is to update to a fixed version rather than relying on a workaround.