CVE-2018-4237 is a privilege-escalation vulnerability in the libxpc component affecting iOS before 11.4, macOS before 10.13.5, tvOS before 11.4, and watchOS before 4.3.1. According to the available description, the flaw is caused by a logic error in libxpc that can be triggered by a crafted application. Successful exploitation allows an attacker to gain elevated privileges on the affected device or 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 contains a single Metasploit module (modules/exploits/osx/local/libxpc_mitm_ssudo.rb) that exploits CVE-2018-4237, a local privilege escalation vulnerability in Apple's macOS (<= 10.13.3). The exploit leverages a flaw in libxpc and the task_set_special_port API, allowing a man-in-the-middle (MitM) attack on the communication between the sudo binary and opendirectoryd. By intercepting and modifying authentication replies, the exploit tricks sudo into granting root privileges. The module uploads an exploit binary and a payload (defaulting to a Meterpreter reverse shell) to a writable directory (default: /tmp), executes the exploit, and, if successful, provides a root shell to the attacker. The code is written in Ruby and is designed to be run within the Metasploit Framework. The main attack vector is local privilege escalation, requiring prior access to the target system.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.