Loading vulnerability…
CVE-2013-4248 is an improper null-byte handling vulnerability in PHP's OpenSSL extension. The openssl_x509_parse function mishandles a NUL character embedded in a domain name within an X.509 certificate Subject Alternative Name. This can cause certificate domain-name validation to accept a certificate for an unintended hostname. PHP versions before 5.4.18 and 5.5.x before 5.5.2 are affected; HP-UX Web Server Suite releases containing the vulnerable PHP build are also affected.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PHP vulnerability enabling a man-in-the-middle attack in affected HP-UX Apache Web Server Suite deployments.
A medium-severity PHP OpenSSL module certificate-validation flaw. Improper handling of NUL characters in Subject Alternative Name domain names can enable a man-in-the-middle attacker using a legitimately CA-issued crafted certificate to spoof arbitrary SSL servers.
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.