A vulnerability in the Content Security Policy (CSP) implementation in the Messages application on Apple OS X prior to version 10.11.4 allows remote attackers to bypass CSP restrictions and obtain sensitive information by leveraging the ability to inject or use a javascript: URL.
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 exploit for CVE-2016-1764, a vulnerability in Apple's Messages (iMessage) client for OS X Yosemite and El Capitan. The exploit leverages the application's use of an embedded WebKit instance that does not enforce the same-origin policy, allowing JavaScript execution via a crafted 'javascript:' URI link. When a victim clicks the malicious link, attacker-controlled JavaScript is executed in the context of the Messages app, enabling arbitrary file reads via XMLHttpRequest to 'file://' URIs. The payload (payload.js) first determines the current user's username by reading the system plist, then locates and exfiltrates the iMessage chat database and all referenced attachments to an attacker-controlled server (extraction_server.py, a Python Tornado web server). The exploit_list.txt file contains a sample malicious URI for use in attacks. The repository is structured with a detailed README explaining the vulnerability and attack chain, a Python server for receiving exfiltrated data, the JavaScript payload, and a sample exploit link. The main exploit capabilities are remote exfiltration of sensitive user data (messages and attachments) from a vulnerable OS X system, requiring only that the victim click a malicious link in iMessage.
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.