dbcve.org
Flash PlayerApplication · Adobe

CVE-2013-0647

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
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 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2013-0638.

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

Memory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution or denial of service via unspecified vectors. The flaw affects multiple platforms (Windows, Mac OS X, Linux, Android) and is distinct from the related CVE-2013-0638.

MitigationUpdate Adobe Flash Player to versions 10.3.183.63+/11.6.602.168+ (Windows), 11.6.602.167+ (Mac), 11.2.202.270+ (Linux), 11.1.111.43+ (Android 2.x/3.x), 11.1.115.47+ (Android 4.x), and Adobe AIR/SDK to 3.6.0.597+/3.6.0.599+ respectively.

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 installed Adobe Flash Player version on Windows
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion, or check the file version of NPSWF32.dll in the browser plugins folder (typically C:\Windows\System32\Macromed\Flash\ or browser-specific locations).
    Affected if The installed version falls within any of these vulnerable ranges: 10.3.x before 10.3.183.63/10.3.183.61, 11.1.x before 11.1.111.43 or 11.1.115.47, 11.2.x before 11.2.202.270, or 11.6.x before 11.6.602.168 (Windows) or 11.6.602.167 (Mac).
  2. Identify installed Adobe Flash Player version on Mac OS X
    Check the file version of Flash Player.plugin in /Library/Internet Plug-Ins/ or ~/Library/Internet Plug-Ins/, or inspect the bundle info of the Flash Player component within the browser application.
    Affected if The installed version is any vulnerable version listed in the affected ranges for Mac (11.6.x before 11.6.602.167, 11.1.x before 11.1.111.43 or 11.1.115.47 for Android, etc.).
  3. Identify installed Adobe Flash Player version on Linux
    Check the file version of libflashplayer.so in the browser plugins directory (typically /usr/lib/flash-plugin/ or /usr/lib/mozilla/plugins/), or run 'rpm -q flash-plugin' or 'dpkg -l flashplugin-installer' if installed via package manager.
    Affected if The installed version is 11.2.x before 11.2.202.270.
  4. Check for Adobe AIR runtime installation and version
    On Windows, check Add/Remove Programs for Adobe AIR, or inspect the version in C:\Program Files\Adobe\Adobe AIR\Versions\1.0\AIRVersion.ini. On Mac, check /Applications/Adobe AIR Installer.app or run 'defaults read /Applications/Adobe AIR Installer.app/Contents/Info CFBundleVersion'.
    Affected if The installed Adobe AIR version is lower than 3.6.0.597.
  5. Check for Adobe AIR SDK installation and version
    Inspect the AIR SDK version file in the SDK installation directory (typically contains a file like AIRSDKReadme.txt or version.xml indicating the SDK version).
    Affected if The installed Adobe AIR SDK version is lower than 3.6.0.599.

The environment is affected if Adobe Flash Player version is within any of the vulnerable version ranges (10.3.x, 11.1.x, 11.2.x, or 11.6.x before the fixed versions) OR if Adobe AIR runtime is below 3.6.0.597 OR if Adobe AIR SDK is below 3.6.0.599.

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

Update Adobe Flash Player to versions 10.3.183.63+/11.6.602.168+ (Windows), 11.6.602.167+ (Mac), 11.2.202.270+ (Linux), 11.1.111.43+ (Android 2.x/3.x), 11.1.115.47+ (Android 4.x), and Adobe AIR/SDK to 3.6.0.597+/3.6.0.599+ respectively.

Recommended fix High confidence

Adobe Flash Player: 10.3.183.63/10.3.183.61 (10.3 branch), 11.6.602.168/11.6.602.167/11.2.202.270/11.1.111.43/11.1.115.47 (11.x branch); Adobe AIR: 3.6.0.597; Adobe AIR SDK: 3.6.0.599

  1. 1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the player or visiting adobe.com/software/flash/about
  2. 2. Identify the installed Adobe AIR version by checking 'About Adobe AIR' in the application or the AIR version in system settings
  3. 3. For Windows users: Download and install Flash Player 10.3.183.63 or 11.6.602.168 (depending on your branch) from the official Adobe website
  4. 4. For Mac OS X users: Download and install Flash Player 10.3.183.61 or 11.6.602.167 (depending on your branch) from the official Adobe website
  5. 5. For Linux users: Download and install Flash Player 10.3.183.61 or 11.2.202.270 (depending on your branch) from the official Adobe website
  6. 6. For Android users: Update Flash Player via Google Play Store to 11.1.111.43 (for Android 2.x/3.x) or 11.1.115.47 (for Android 4.x)
  7. 7. Download and install Adobe AIR 3.6.0.597 or later from the official Adobe website
  8. 8. If using Adobe AIR SDK, upgrade to version 3.6.0.599 or later
Caveat Ensure browser compatibility with the new Flash Player version; some older plugins or extensions may need updating

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0647 — 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-0647 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