Loading vulnerability…
A vulnerability in sudoedit in Sudo before version 1.8.15 allows local users to escalate privileges by exploiting a symlink attack. The issue arises when a file path in /etc/sudoers is defined using multiple wildcards (e.g., "/home///file.txt"). An attacker can create a symlink at a matching path, causing sudoedit to operate on an unintended file, potentially leading to privilege escalation.
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 provides a local privilege escalation exploit for CVE-2015-5602, targeting sudo versions 1.8.13 and below (<=1.8.14) on Linux. The exploit leverages a misconfiguration in the sudoers file that allows a user to run sudoedit on a path with double wildcards (e.g., /home/*/*/esc.txt) without a password. The exploit script (exploit.sh) creates a symlink from a user-controlled path to /etc/shadow, sets a custom EDITOR that overwrites the root password hash, and invokes sudoedit to trigger the vulnerability. The Dockerfile sets up a vulnerable environment with the necessary sudo version and sudoers configuration for testing. The main fingerprintable endpoints are the /etc/shadow file (target of the attack), the sudoers entry for /home/*/*/esc.txt, and the custom editor script at /tmp/edit. The exploit is operational and provides root access by changing the root password to a known value.
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.