dbcve.org
Flash PlayerApplication · Adobe

CVE-2013-0649

HIGH · 10.0 CVSS v2.0 Published 2013-02-12
Fix available
A fix is available. Upgrade to 3.6.0.597 / 3.6.0.599 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Use-after-free vulnerability in Adobe Flash Player before 10.3.183.63 and 11.x before 11.6.602.168 on Windows, before 10.3.183.61 and 11.x before 11.6.602.167 on Mac OS X, before 10.3.183.61 and 11.x before 11.2.202.270 on Linux, before 11.1.111.43 on Android 2.x and 3.x, and before 11.1.115.47 on Android 4.x; Adobe AIR before 3.6.0.597; and Adobe AIR SDK before 3.6.0.599 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2013-0644 and CVE-2013-1374.

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 confidence

Use-after-free vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution. This is a memory corruption flaw where the software attempts to use memory after it has been freed, potentially enabling remote code execution by attackers.

MitigationUpgrade Adobe Flash Player to version 10.3.183.63+/11.6.602.168+ (Windows), 10.3.183.61+/11.6.602.167+ (Mac), 10.3.183.61+/11.2.202.270+ (Linux), 11.1.111.43+ (Android 2.x/3.x), or 11.1.115.47+ (Android 4.x); upgrade Adobe AIR to 3.6.0.597+ and AIR SDK to 3.6.0.599+.

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
Flash PlayerApplication
Affected:>= 10.3, < 10.3.183.63>= 11.6, < 11.6.602.168>= 10.3, < 10.3.183.61>= 11.2, < 11.2.202.270>= 11.1, < 11.1.111.43>= 11.1, < 11.1.115.47>= 11.6, < 11.6.602.167
AirApplication
Affected:< 3.6.0.597
Air SdkApplication
Affected:< 3.6.0.599

CVSS 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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Adobe Flash Player version
    Open a browser and navigate to 'about:flash' (Firefox) or check Help > About Adobe Flash Player. On Windows, also check the version in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer or HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\FlashPlayer. On Mac, check /Library/Application Support/Adobe/Flash Player/ or the browser plugin info.
    Affected if The installed version falls within: 10.3 to 10.3.183.62 (Windows), 10.3 to 10.3.183.60 (Mac/Linux), 11.6 to 11.6.602.166 (Windows), 11.6 to 11.6.602.165 (Mac), 11.2 to 11.2.202.269 (Linux), 11.1 to 11.1.111.42 (Android 2.x/3.x), or 11.1 to 11.1.115.46 (Android 4.x)
  2. Identify Adobe AIR version
    On Windows, check Add/Remove Programs for 'Adobe AIR' and note the version number displayed. On Mac, navigate to /Applications/Adobe AIR and right-click to Get Info. You can also run 'Adobe AIR Application Installer' and the version appears in the window title or check %ProgramFiles%\Adobe\AIR\versions.txt.
    Affected if The installed Adobe AIR version is lower than 3.6.0.597
  3. Identify Adobe AIR SDK version
    Check the version file in the AIR SDK installation directory. Look for a version manifest or version.txt file typically located in the root SDK directory, or check the properties of the AIRSDKInstaller executable if used.
    Affected if The installed Adobe AIR SDK version is lower than 3.6.0.599

You are affected if any installed Adobe Flash Player version, Adobe AIR version, or Adobe AIR SDK version falls within the affected ranges listed above.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.6.0.597 / 3.6.0.599 / 10.3.183.61 or later
Fixed in 3.6.0.5973.6.0.59910.3.183.61
Interim mitigation

Upgrade Adobe Flash Player to version 10.3.183.63+/11.6.602.168+ (Windows), 10.3.183.61+/11.6.602.167+ (Mac), 10.3.183.61+/11.2.202.270+ (Linux), 11.1.111.43+ (Android 2.x/3.x), or 11.1.115.47+ (Android 4.x); upgrade Adobe AIR to 3.6.0.597+ and AIR SDK to 3.6.0.599+.

Recommended fix High confidence

Adobe Flash Player 10.3.183.63+/11.6.602.168+/11.2.202.270+ and Adobe AIR 3.6.0.597+ / AIR SDK 3.6.0.599+

  1. 1. Identify the current Adobe Flash Player version installed by navigating to 'About Flash Player' in the player context menu or visiting the Adobe version check page
  2. 2. Identify the current Adobe AIR version from the Windows Programs and Features (or Mac Applications folder)
  3. 3. Based on the operating system (Windows, Mac OS X, or Linux), download the corresponding fixed Flash Player version from the Adobe Security Bulletins page: 10.3.183.63 (Windows), 10.3.183.61 (Mac/Linux), 11.6.602.168 (Windows), 11.6.602.167 (Mac), or 11.2.202.270 (Linux
  4. 4. For Android devices, download Flash Player 11.1.111.43 (for Android 2.x/3.x) or 11.1.115.47 (for Android 4.x) from the Google Play Store or Adobe
  5. 5. For Adobe AIR, download and install version 3.6.0.597 or later from the Adobe AIR download page
  6. 6. For developers using Adobe AIR SDK, download AIR SDK version 3.6.0.599 or later from the Adobe AIR SDK page
  7. 7. Restart all browsers and applications that use Flash Player after installation
  8. 8. Verify the installed version matches or exceeds the fixed versions listed above
Caveat Upgrading Flash Player may cause compatibility issues with older web applications or browser plugins designed for earlier Flash versions; test critical web applications after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flash Player Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0649 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0649 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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