Loading vulnerability…
A race condition in the mail.local(8) utility on NetBSD versions 6.0 through 7.0.1 allows local users to exploit a symlink attack between lstat(2) and open(2) calls. Because mail.local is setuid root, this flaw enables attackers to change ownership or append data to arbitrary files, potentially leading to privilege escalation. The vulnerability was discovered and patched in July 2016.
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/netbsd_mail_local.rb) that exploits a local privilege escalation vulnerability (CVE-2016-6253) in NetBSD's mail.local utility. The exploit targets NetBSD versions 6.0-6.1.5 and 7.0-7.0.1, leveraging a race condition to overwrite the SUID atrun binary. The module drops and compiles a C exploit on the target, which manipulates mailbox files and symlinks to win a race and gain write access to atrun. It then overwrites atrun with a shell script that creates a setuid shell at /tmp/ksh. When cron executes atrun, the attacker gains a root shell, and the original atrun is restored. The Metasploit payload is delivered via a temporary file and executed by the setuid shell. The module is operational and requires local access, a writable /tmp directory, and a vulnerable system configuration. The only file in the repository is the Metasploit module, which contains both Ruby and embedded C code.
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.