Loading vulnerability…
A buffer overflow vulnerability exists in the IOHIDFamily component of Apple OS X prior to version 10.10.3. The flaw allows local users to trigger a buffer overflow via unspecified vectors, potentially leading to arbitrary code execution with elevated privileges.
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 contains a local privilege escalation exploit for macOS (Darwin) systems running vulnerable versions of the XNU kernel (10.10.x). The exploit targets a heap overflow vulnerability in the IOHIDFamily kernel extension. The main exploit logic is implemented in Objective-C and C, with the entry point in 'main.m'. The exploit works by performing heap feng shui to position a C++ object in the kernel heap, then triggering a heap overflow to overwrite the object's vtable pointer. This allows the attacker to execute a crafted ROP chain in kernel context, ultimately running a payload that sets the current process's credentials to root (UID 0), disables SMEP, and spawns a root shell. The repository also includes 'patch.c' and 'unpatch.c' utilities to patch or restore the vulnerable function in the IOHIDFamily kernel extension binary. The exploit requires local access and is not a remote exploit. The code is mature and operational, providing a working privilege escalation if the target is vulnerable. The main fingerprintable endpoints are the kernel binary files and the IOHIDFamily kernel extension file, which are accessed and modified during exploitation and patching.
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.