Multiple stack-based buffer overflows in Apple QuickTime for Windows before version 7.7.2 can be triggered through a crafted TeXML file. Successful exploitation can result in arbitrary code execution or an 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.
This repository contains a single Metasploit module: 'apple_quicktime_texml.rb', which exploits a stack-based buffer overflow vulnerability (CVE-2012-0663) in Apple QuickTime (versions 7.6.9, 7.7.0, and 7.7.1) on Windows XP SP3. The exploit works by generating a specially crafted TeXML file (default name: msf.xml) with a maliciously constructed 'Style' element. When a user opens this file with a vulnerable version of QuickTime, the overflow is triggered, allowing arbitrary code execution via SEH overwrite. The module allows the attacker to select a payload, which is embedded in the file and executed upon successful exploitation. The attack vector is local, requiring user interaction to open the malicious file. The code is written in Ruby and is designed to be used within the Metasploit framework.
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.