Renderer crash via unchecked root element
Published Feb 15, 2022 · Updated Nov 3, 2025
Null pointer dereference in the SVG++ 1.3.0 demo renderer allows remote attackers to crash it through a crafted rootless XML document. The renderer passes XMLDocument::getRoot() directly to load_document without checking whether parsing returned a root element. Exploitation requires the document to be opened by the demo renderer and terminates that process through a zero-address read.
Summary
What happened
Null pointer dereference in the SVG++ 1.3.0 demo renderer allows remote attackers to crash it through a crafted rootless XML document. The renderer passes XMLDocument::getRoot() directly to load_document without checking whether parsing returned a root element. Exploitation requires the document to be opened by the demo renderer and terminates that process through a zero-address read.
The record
- CVE
- CVE-2021-44960
- Published
- Feb 15, 2022
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 15, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Rootless XML crash proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo