CVE-2015-0273 is a use-after-free vulnerability in PHP's date extension affecting PHP versions before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6. Crafted serialized data containing R or r reference specifiers can trigger unsafe object handling while initializing DateTimeZone objects through php_date_timezone_initialize_from_hash or DateTime objects through php_date_initialize_from_hash. The resulting dangling-memory condition can be leveraged for arbitrary code execution.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A historical PHP unserialize use-after-free vulnerability cited as prior art for the same bug class.
A PHP use-after-free vulnerability, identified as CVE-2015-0273, reported here as used against an encrypted PHPWind unserialize() call to obtain shell access on the target server.
A vulnerability addressed in HP Matrix Operating Environment 7.5.0.
Remote arbitrary-code-execution vulnerability affecting HP System Management Homepage (SMH).
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.