Loading vulnerability…
A buffer overflow vulnerability exists in the getvolattrlist function of the Apple Kernel component, affecting iOS before 11.4, macOS before 10.13.5, tvOS before 11.4, and watchOS before 4.3.1. The flaw allows a crafted application to trigger a buffer overflow, potentially leading to arbitrary code execution with kernel 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 (1 hidden).
This repository contains a full iOS local kernel exploit for CVE-2018-4243 (p0 issue 1564), targeting iOS 11.0 through 11.3.1. The exploit is implemented as an Objective-C iOS application, with the main logic in C (sploit.c, kmem.c, offsets.m/h). The exploit abuses a vulnerability in the getvolattrlist syscall, allowing an attacker to write 8 zero bytes past the end of a kalloc.16 allocation in kernel memory. By carefully grooming kernel heap allocations, the exploit targets the reference count of a struct ipc_port, creating a use-after-free condition and ultimately gaining a dangling mach port. This is leveraged to craft a fake kernel task port (tfp0), granting arbitrary kernel read/write access. The exploit is operational, with a reported reliability of around 30%, and includes cleanup routines to avoid panicking the device. The code is structured as a standard Xcode iOS project, with entry points in main.m and AppDelegate.m, and the exploit logic in sploit.c. The README provides a detailed technical explanation of the bug, exploitation strategy, and usage notes. No network endpoints are present; the attack vector is local, requiring code execution on the target device.
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.