CVE-2014-3981 is a symlink-following vulnerability in the PHP configure-script support logic derived from acinclude.m4 in PHP 5.5.13 and earlier. During a glibc-related configuration check, the script uses a predictable temporary file without safely preventing symbolic-link substitution. A local attacker can pre-create a symbolic link at that temporary-file location so that a subsequent configure execution overwrites an attacker-selected file accessible to the user running the script.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PHP vulnerability that permits local modification of data in affected HP-UX Apache Web Server Suite deployments.
A local file-access vulnerability in PHP included in the HP-UX Apache Web Server Suite bulletin.
A low-severity local arbitrary-file-overwrite vulnerability in PHP's acinclude.m4/configure script. A local user can exploit a symlink attack involving /tmp/phpglibccheck; PHP 5.5.13 and earlier are affected.
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.