CVE-2018-4185 is an information disclosure vulnerability affecting iOS before 11.3, tvOS before 11.3, watchOS before 4.3, and macOS before High Sierra 10.13.4. The vulnerability arises from improper handling of program state transitions, which could allow unauthorized access to sensitive information during these transitions.
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 (PoC) iOS application demonstrating a kernel information leak present in iOS 11.2 on arm64 devices. The vulnerability arises from the __ARM_KERNEL_PROTECT__ feature, which inadvertently causes the kernel address of the function Lel0_synchronous_vector_64_long to be stored in register x18. This value is then accessible to userland via the thread_get_state() API, allowing an attacker to determine the kASLR slide and bypass kernel address space layout randomization protections. The repository is structured as a standard Xcode project for an iOS app. The main exploit logic resides in x18_leak.c and x18_leak.h, which implement the x18_leak() function. This function retrieves the current thread's state, extracts the value of register x18, and returns it if it matches the expected kernel address range. The AppDelegate.m file calls this function at application launch and prints the leaked kernel address to stdout before exiting. The rest of the files are standard iOS app scaffolding (storyboards, asset catalogs, etc.). No network or remote attack vector is present; the exploit must be run locally on a vulnerable device. The exploit does not provide code execution or privilege escalation, but it enables further exploitation by leaking a critical kernel address.
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.