Negative length handling flaw in libexpat XML_ParseBuffer
CVE-2024-45490 is a vulnerability in libexpat before 2.6.3. According to the provided content, xmlparse.c does not reject a negative length passed to XML_ParseBuffer. This indicates improper input validation in the parser’s buffer-length handling, where a caller-controlled negative length is accepted instead of being rejected. Apple also characterizes this as an open-source vulnerability affecting Apple software among other projects.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A sandbox-escape issue addressed with improved checks.
An open-source vulnerability affecting Apple Vision Pro where a remote attacker could cause app termination or achieve arbitrary code execution; CVE assigned by a third party.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.