Loading vulnerability…
CVE-2010-1297 is a memory corruption vulnerability in Adobe Flash Player, Adobe AIR, and Adobe Reader/Acrobat components that embed Flash, specifically involving authplay.dll and the ActionScript Virtual Machine 2 (AVM2) handling of the ActionScript newfunction instruction. Adobe Flash Player before 9.0.277.0 and 10.x before 10.1.53.64, Adobe AIR before 2.0.2.12610, and Adobe Reader/Acrobat 9.x before 9.3.3 and 8.x before 8.2.3 on Windows and Mac OS X are affected. A remote attacker can trigger the flaw using crafted SWF content; malformed use of the AVM2 newfunction instruction can cause an exploitable crash due to memory corruption. The issue was exploited in the wild in June 2010, and public exploit code was available.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit module targeting CVE-2010-1297, a critical vulnerability in Adobe Flash Player (versions 9.x and 10.0) and applications embedding it (such as Adobe Reader and Acrobat 9.x) on Windows. The exploit works by generating a malicious PDF file ('msf.pdf') that embeds a specially crafted SWF (Flash) file. When the PDF is opened in a vulnerable environment, JavaScript (AcroJS) is used to perform a heap spray, and the embedded SWF triggers an invalid pointer dereference, leading to arbitrary code execution. The exploit supports custom Metasploit payloads, allowing the attacker to execute arbitrary code on the target system. The module is operational and leverages a DEP bypass technique, though its reliability may vary across Windows versions due to hardcoded syscall numbers. The main attack vector is a malicious file (PDF), and the primary fingerprintable endpoints are the generated PDF and embedded SWF file. The code is written in Ruby and is structured as a standard Metasploit exploit module.
This repository contains a single Metasploit module (adobe_flashplayer_newfunction.rb) that exploits CVE-2010-1297, a vulnerability in Adobe Flash Player 9.x and 10.0 (and applications embedding it, such as Adobe Reader/Acrobat 9.x) on Windows. The exploit works by serving a malicious PDF file containing a specially crafted SWF (Flash) file. When the victim opens the PDF, embedded JavaScript performs a heap spray, and the SWF triggers an invalid pointer use, allowing arbitrary code execution. The exploit includes a DEP bypass (using a hardcoded syscall, which may limit reliability across Windows versions). The payload is customizable via Metasploit and is delivered as shellcode embedded in the PDF. The module references the required SWF file (CVE-2010-1297.swf) and constructs the malicious PDF on the fly. The attack vector is a browser or document (PDF) opened by the victim. The repository is operational and suitable for real-world exploitation with Metasploit.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability included in multiple exploit kits according to the table.
A zero-day exploit used by the GREF threat group in 2010 as part of watering hole and targeted attack activity.
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.