Loading vulnerability…
CVE-2024-10224 is a local privilege escalation vulnerability in the Perl Module::ScanDeps library, as used by the needrestart tool (prior to version 1.36). If unsanitized input is passed to ScanDeps, a local attacker can execute arbitrary shell commands as root by supplying a filename containing a pipe character (e.g., 'commands|') to open(), or by passing arbitrary strings to eval(). This is due to unsafe handling of user-controlled input in open() and eval() calls within ScanDeps, which is invoked by needrestart during interpreter scanning.
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.
Repository contains a minimal proof-of-concept for local command execution via needrestart configuration parsing. Structure: (1) README.md describing CVE-2024-11003 and referencing related CVE-2024-10224 in Modules::ScanDeps, plus usage instructions; (2) exploit.conf containing a single directive: exec "/bin/sh","-p";. The intended exploitation flow is to run needrestart (README says 'needstart') with elevated privileges and point it at the malicious config using -c, causing the program/library path (Modules::ScanDeps) to execute the embedded command and spawn a privileged shell. No network activity, callbacks, or remote endpoints are present; the only fingerprintable artifacts are the config filename and the /bin/sh payload path.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.