Loading vulnerability…
safer-eval versions prior to 1.3.2 are vulnerable to arbitrary code execution due to improper sandboxing. Attackers can craft payloads that leverage constructor properties to escape the intended sandbox environment and execute arbitrary code on the host system.
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.
This repository is a proof-of-concept exploit for CVE-2019-10760, targeting the 'safer-eval' npm package (version 1.3.1 and below) in Node.js environments. The main exploit is implemented in 'index.js', which crafts a payload that leverages JavaScript's Function constructor to escape the 'safer-eval' sandbox and execute arbitrary shell commands via Node's 'child_process' module. The payload writes the process environment variables to '/tmp/rce' as evidence of successful code execution. The repository includes standard Node.js project files ('package.json', 'package-lock.json') and a brief README. No network endpoints are present; the exploit demonstrates local command execution on the vulnerable host.
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.