CVE-2020-27949 is a vulnerability in macOS where a malicious application could cause unexpected changes in memory belonging to processes traced by DTrace. The vulnerability arises due to insufficient checks in the DTrace subsystem, allowing unauthorized actions on traced process memory.
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 demonstrates a local privilege escalation and memory disclosure exploit for CVE-2020-27949, affecting macOS systems prior to Big Sur 11.1. The exploit leverages the world-writable permissions of /dev/fasttrap, which lacks proper privilege checks, allowing any user to create DTrace probes in other processes. The main exploit is implemented in 'exploit.cpp', which interacts with the fasttrap device to create probes in a victim process (whose PID and target memory address are provided by the user). The exploit then uses the FASTTRAPIOC_GETINSTR ioctl to read memory from the victim process, even if it is running as root, as long as it is being traced by DTrace. The repository includes a simple victim application ('target.cpp') and a DTrace script ('libc_monitor.d') to facilitate demonstration. The exploit does not require root privileges and can be used by any local user on a vulnerable system. The code is a proof-of-concept and does not include weaponized payloads, but demonstrates the ability to read and potentially write arbitrary memory in another process.
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.