Loading vulnerability…
CVE-2018-1000888 affects PEAR Archive_Tar version 1.4.3 and earlier. The vulnerability is in the Archive_Tar class, which performs multiple file operations using the archive header field $v_header['filename'] as input, including functions such as file_exists, is_file, and is_dir. When extract() is invoked without a specific prefix path, an attacker can supply a crafted tar archive whose filename field uses a phar:// stream wrapper path pointing to a malicious PHAR file. In PHP, accessing a PHAR path can trigger implicit unserialization of PHAR metadata, resulting in object injection. This can invoke magic methods such as destructors in already loaded classes. The provided context specifically notes that Archive_Tar object injection can lead to arbitrary file deletion because @unlink($this->_temp_tarname) may be reached during object destruction. If a suitable gadget chain from another loaded class is available, exploitation may also lead to remote code execution or file modification. The issue was fixed in Archive_Tar 1.4.4.
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.
extract() on attacker-controlled tar content without a safe extraction path policy. Limiting availability of exploitable gadget chains in the PHP application may reduce impact, but this is not a reliable substitute for patching. No specific temporary workaround is provided in the advisory content.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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.