CVE-2010-1297
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAdobe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMemory corruption vulnerability in Adobe Flash Player and Reader/Acrobat's ActionScript Virtual Machine 2 (AVM2) related to the newfunction instruction in authplay.dll. Attackers exploit crafted SWF content to achieve arbitrary code execution through heap manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.0.2.12610< 9.0.277.0>= 10.0, < 10.1.53.64>= 8.0, < 8.2.3>= 9.0, < 9.3.3>= 11.0, <= 11.2= 10.0= 11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Adobe Flash Player version in WindowsOpen a web browser and navigate to a Flash version check page (such as the Adobe version checker), or check the authplay.dll file properties in the System32 or SysWOW64 directoryAffected if Version is less than 9.0.277.0, OR between 10.0 and 10.1.53.63 (inclusive)
-
Check Adobe Flash Player version on Linux/SuseRun 'rpm -q flash-player' or check the installed package version via the package managerAffected if Version is less than 9.0.277.0, OR between 10.0 and 10.1.53.63 (inclusive)
-
Check Adobe AIR versionRun 'air -version' from command line, or check the installation directory for the AIR runtime versionAffected if Version is less than 2.0.2.12610
-
Check Adobe Acrobat versionLaunch Acrobat, go to Help > About Adobe Acrobat, or check the Windows registry under HKLM\Software\Adobe\Acrobat\VersionAffected if Version is 8.x and less than 8.2.3, OR version is 9.x and less than 9.3.3
-
Check Adobe Reader versionLaunch Reader, go to Help > About Adobe Reader, or check the Windows registry under HKLM\Software\Adobe\Acrobat Reader\VersionAffected if Version is 8.x and less than 8.2.3, OR version is 9.x and less than 9.3.3
A system is affected if any Adobe Flash Player, AIR, Acrobat, or Reader installation matches the vulnerable version ranges and can process SWF content (which is the default behavior for unpatched installations).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0.2.126108.2.39.0.277.0
Deploy vendor-provided patches: update Adobe Flash Player to 10.1.53.64+/9.0.277.0+, Adobe AIR to 2.0.2.12610+, and Adobe Reader/Acrobat to 9.3.3+/8.2.3+ across all affected Windows and Mac systems.
Adobe Flash Player 10.1.53.64+, Adobe AIR 2.0.2.12610+, Adobe Reader/Acrobat 8.2.3+ or 9.3.3+
- 1. Identify which Adobe product is installed (Flash Player, AIR, or Acrobat/Reader) using system inventory or application listings
- 2. For Adobe Flash Player: Uninstall the vulnerable version and install Flash Player 10.1.53.64 or later (or preferably migrate to Ruffle as Flash is EOL)
- 3. For Adobe AIR: Uninstall the vulnerable version and install AIR 2.0.2.12610 or later (AIR is EOL; migrate to HTML5 alternatives)
- 4. For Adobe Reader/Acrobat on Windows/Mac: Uninstall vulnerable version and install version 8.2.3 (for 8.x) or 9.3.3 (for 9.x) or later
- 5. For OpenSUSE/Linux Enterprise systems: Run 'sudo zypper update' or 'sudo zypper patch' to apply Adobe security updates from vendor repositories
- 6. Verify successful installation by checking application version numbers
- 7. Restart any affected browsers or applications
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- blog.zynamics.com
- secunia.com
- secunia.com
- www.adobe.com
- www.vupen.com
- www.vupen.com
- lists.apple.com
- lists.opensuse.org
- lists.opensuse.org
- security.gentoo.org
- securitytracker.com
- securitytracker.com
- securitytracker.com
- securitytracker.com
- www.exploit-db.com
- www.kb.cert.org
- www.securityfocus.com
- www.securityfocus.com
- www.us-cert.gov
- www.us-cert.gov
- exchange.xforce.ibmcloud.com
- blog.zynamics.com
- community.websense.com
- itrc.hp.com
- secunia.com
- secunia.com
- secunia.com
- support.apple.com
- www.adobe.com
- www.adobe.com
- www.osvdb.org
- www.redhat.com
- www.redhat.com
- www.turbolinux.co.jp
- www.vupen.com
- www.vupen.com
- www.vupen.com
- www.vupen.com
- www.vupen.com
- www.vupen.com
- www.vupen.com
- www.vupen.com
- www.vupen.com
- oval.cisecurity.org
- www.cisa.gov
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-1297 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data