Loading vulnerability…
The slapper function in chkrootkit versions prior to 0.50 fails to properly quote file paths, allowing a local attacker to execute arbitrary code by placing a malicious executable in a path processed by chkrootkit. This vulnerability is only exploitable if /tmp is not mounted with the noexec option, as the attack relies on executing files from /tmp.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit module (modules/exploits/unix/local/chkrootkit.rb) that exploits a local privilege escalation vulnerability in chkrootkit versions before 0.50 (CVE-2014-0476). The vulnerability arises because chkrootkit will execute any file named /tmp/update as root during its scheduled scan (typically via cron every 24 hours). The exploit module writes a shell script containing the attacker's payload to /tmp/update, sets it as executable, and waits for chkrootkit to run and execute the payload as root. The module is weaponized, supporting arbitrary payloads via the Metasploit framework, and is intended for use by an attacker who already has local access to the target system. The main fingerprintable endpoints are the /tmp/update file (used for privilege escalation) and the chkrootkit binary path. The exploit is reliable but may take up to 24 hours to trigger, depending on the cron schedule.
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.