CVE-2017-7117 is a memory corruption vulnerability in the WebKit component used by multiple Apple products, including iOS, Safari, iCloud for Windows, iTunes for Windows, and tvOS, prior to version 11 (or 7.0/12.7 for iCloud/iTunes). The vulnerability can be triggered by a remote attacker through a specially crafted web page, leading to memory corruption and potentially 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 contains a proof-of-concept (POC) exploit for CVE-2017-7117, a type confusion and use-after-free vulnerability in JavaScriptCore (JSC) affecting iOS 10.3.4 and earlier, Safari before 11.0, and WebKitGTK 2.16.0. The main exploit is implemented in 'poc.js', which demonstrates how to trigger the vulnerability to leak the memory address of a JavaScript object (addrof primitive). The exploit works by manipulating the JIT compiler's type inference, freeing a large array, and then spraying memory to locate a target object. The README provides detailed background, setup instructions, and explains the exploit's mechanism. The code is a POC and does not provide full arbitrary read/write or code execution, but establishes a crucial primitive for further exploitation. No network or file system endpoints are present; the attack vector is browser-based, requiring execution in a vulnerable JSC environment.
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 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.