Loading vulnerability…
CVE-2018-4121 is a memory corruption vulnerability in the WebKit component used by multiple Apple products, including iOS (before 11.3), Safari (before 11.1), iCloud for Windows (before 7.4), iTunes for Windows (before 12.7.4), tvOS (before 11.3), and watchOS (before 4.3). The vulnerability can be triggered by a remote attacker through a specially crafted web page, leading to memory corruption and potentially allowing arbitrary code execution or application crash.
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 is a proof-of-concept (POC) exploit for CVE-2018-4121, a remote code execution vulnerability in Safari 11.0.3 on macOS 10.13.3. The exploit leverages a WebAssembly section parsing bug to achieve arbitrary code execution in the browser context. The structure includes: - 'exploit.html': The main page to be loaded in Safari, which includes the exploit and payload scripts. - 'exploit.js': The core exploit logic, which performs heap spraying, info leak, and vtable manipulation to redirect execution to attacker-controlled code. - 'alert_payload.m': An example Objective-C payload that, when compiled as a dylib, shows an alert dialog. Any dylib can be used as a payload. - 'file_to_jsarray.py': A helper script to convert a compiled dylib into a JavaScript array for inclusion as 'payload.js'. - 'README.md': Documentation and usage instructions. To use the exploit, an attacker compiles their payload as a dylib, converts it to a JS array, serves the files, and lures a target to visit 'exploit.html' in Safari. The exploit is not fully reliable and is version-specific due to hardcoded offsets. The main attack vector is browser-based, requiring user interaction (visiting a malicious page).
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.