CVE-2010-1297

KEVAdobe Flash Player Memory Corruption Vulnerability

Description

Adobe Flash Player contains a memory corruption vulnerability that allows remote attackers to execute code or cause denial-of-service (DoS).

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 and Acrobat 9.x before 9.3.3, and 8.x before 8.2.3 on Windows and Mac OS X, allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via crafted SWF content, related to authplay.dll and the ActionScript Virtual Machine 2 (AVM2) newfunction instruction, as exploited in the wild in June 2010.

CVSS 3.1 vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

PublishedJun 8, 2010

Last modifiedJun 16, 2026

Added to KEVJun 8, 2022

Remediation dueJun 22, 2022

References

blog.zynamics.com/2010/06/09/analyzing-the-currently-exploited-0-day-for-adobe-reader-and-adobe-flash/Exploit
community.websense.com/blogs/securitylabs/archive/2010/06/09/having-fun-with-adobe-0-day-exploits.aspxBroken Link
itrc.hp.com/service/cki/docDisplay.do?docId=emr_na-c02273751Broken Link
lists.apple.com/archives/security-announce/2010//Nov/msg00000.htmlMailing ListThird Party Advisory
lists.opensuse.org/opensuse-security-announce/2010-06/msg00000.htmlMailing ListThird Party Advisory
lists.opensuse.org/opensuse-security-announce/2010-06/msg00001.htmlMailing ListThird Party Advisory
secunia.com/advisories/40026Broken LinkVendor Advisory
secunia.com/advisories/40034Broken LinkVendor Advisory
secunia.com/advisories/40144Broken Link
secunia.com/advisories/40545Broken Link
secunia.com/advisories/43026Broken Link
security.gentoo.org/glsa/glsa-201101-09.xmlThird Party Advisory

0 recent articles mention this CVE

Risk assessment · High

Actively exploited. Patch immediately.

Exploitation: Confirmed in the wild (CISA KEV)
Federal remediation deadline: Overdue by 1587 days
CVSS: 7.8 HIGH
EPSS (30-day exploit probability): 82.5% · top 1% of all CVEs
Weakness: CWE-787

Recommended actions

1.The impacted product is end-of-life and should be disconnected if still in use.
2.Treat as emergency change: patch or isolate internet-facing instances first.
3.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

Assessment is derived automatically from the live signals above; verify against your own asset inventory.