Loading vulnerability…
A buffer over-read vulnerability exists in PHP's Phar extension (ext/phar/phar.c) prior to versions 5.4.40, 5.5.24, and 5.6.8. Remote attackers can trigger this flaw by supplying a crafted length value in conjunction with specially crafted serialized data within a phar archive. The vulnerability is present in the phar_parse_metadata and phar_parse_pharfile functions, which fail to properly validate input, leading to out-of-bounds memory reads. This can result in sensitive information disclosure from process memory or a denial of service via application crash.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.