Flash PlayerApplication · Adobe

CVE-2013-0646

HIGH · 10.0 CVSS v2.0 Published 2013-03-13
Fix available
A fix is available. Upgrade to after 11.6.602.171 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
Integer overflow in Adobe Flash Player before 10.3.183.68 and 11.x before 11.6.602.180 on Windows and Mac OS X, before 10.3.183.68 and 11.x before 11.2.202.275 on Linux, before 11.1.111.44 on Android 2.x and 3.x, and before 11.1.115.48 on Android 4.x; Adobe AIR before 3.6.0.6090; Adobe AIR SDK before 3.6.0.6090; and Adobe AIR SDK & Compiler before 3.6.0.6090 allows attackers to execute arbitrary code via unspecified vectors.

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

Integer overflow vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution via unspecified vectors. The flaw exists in multiple versions across Windows, Mac OS X, Linux, and Android platforms.

MitigationUpdate Adobe Flash Player to 10.3.183.68+, 11.6.602.180+, 11.2.202.275+, 11.1.111.44+, or 11.1.115.48+ (depending on platform); update Adobe AIR/SDK to 3.6.0.6090 or later.

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:<= 11.6.602.171= 11.0= 11.0.1.152= 11.0.1.153= 11.1= 11.1.102.55= 11.1.102.59= 11.1.102.62= 11.1.102.63= 11.1.111.5= 11.1.111.6= 11.1.111.7
Flash Player For AndroidApplication
Affected:<= 11.1.111.43= 10.1.106.17= 10.2.157.51= 10.3.186.7= 11.0.1.153= 11.1.102.59= 11.1.111.5= 11.1.111.6= 11.1.111.7= 11.1.111.8= 11.1.111.9= 11.1.111.10
Adobe Air Sdk And CompilerApplication
Affected:<= 3.6.0.599
Adobe Air SdkApplication
Affected:<= 3.6.0.597= 3.0.0.4080= 3.1.0.488= 3.2.0.2070= 3.3.0.3650= 3.3.0.3690= 3.4.0.2540= 3.4.0.2710= 3.5.0.600= 3.5.0.880= 3.5.0.890= 3.5.0.1060
Adobe AirApplication
Affected:all versions<= 3.6.0.597= 1.0= 1.0.1= 1.0.8.4990= 1.0.4990= 1.1= 1.1.0.5790= 1.5= 1.5.0.7220= 1.5.1= 1.5.1.8210

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. Check Adobe Flash Player version on desktop
    On Windows: Open Control Panel > Programs > Programs and Features, find Adobe Flash Player and note the version. On Mac: Look in /Library/Internet Plug-Ins/ for Flash Player.plugin and check its info. In browsers: Visit adobe.com/software/flash/about/ or type 'about:plugins' in Firefox.
    Affected if Version is 11.6.602.171 or lower, or exactly matches any listed affected version (11.0, 11.0.1.152, 11.0.1.153, 11.1, 11.1.102.55, 11.1.102.59, 11.1.102.62, 11.1.102.63, 11.1.111.5, 11.1.111.6, or 11.1.111.7)
  2. Check Adobe Flash Player for Android version
    On the Android device, go to Settings > Apps > Adobe Flash Player or check the app info. You can also check via adb: 'adb shell pm list packages | grep flash' then 'adb shell dumpsys package <package>'
    Affected if Version is 11.1.111.43 or lower, or exactly matches any listed affected version (10.1.106.17, 10.2.157.51, 10.3.186.7, 11.0.1.153, 11.1.102.59, 11.1.111.5-11.1.111.10)
  3. Check Adobe AIR runtime version on desktop
    Windows: Open Control Panel > Programs > Programs and Features, find Adobe AIR. Mac: Check /Applications/Adobe AIR Installer.app or run 'defaults read /Applications/Adobe\ AIR\ Installer.app/Contents/Info CFBundleVersion'. Or check the Windows registry: HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR\Version
    Affected if Version is 3.6.0.597 or lower, or exactly matches any listed affected version (1.0, 1.0.1, 1.0.8.4990, 1.0.4990, 1.1, 1.1.0.5790, 1.5, 1.5.0.7220, 1.5.1, 1.5.1.8210, or specific 3.x versions)
  4. Check Adobe AIR SDK version
    If you have Adobe AIR SDK installed, check the file 'air-sdk-version.xml' in the SDK directory, or run the AIR developer tools and check the version output. Check the directory where the SDK was extracted.
    Affected if SDK version is 3.6.0.599 or lower (SDK and Compiler), or 3.6.0.597 or lower (SDK), or exactly matches any listed specific version (3.0.0.4080, 3.1.0.488, 3.2.0.2070, 3.3.0.3650, 3.3.0.3690, 3.4.0.2540, 3.4.0.2710, 3.5.0.600, 3.5.0.880, 3.5.0.890, 3.5.0.1060)

The environment is affected if any installed Adobe Flash Player, Adobe AIR runtime, or Adobe AIR SDK version matches the affected ranges listed for CVE-2013-0646.

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 a release after 11.6.602.171
Interim mitigation

Update Adobe Flash Player to 10.3.183.68+, 11.6.602.180+, 11.2.202.275+, 11.1.111.44+, or 11.1.115.48+ (depending on platform); update Adobe AIR/SDK to 3.6.0.6090 or later.

Recommended fix High confidence

Flash Player 11.x: 11.6.602.180 (Windows/Mac), 11.2.202.275 (Linux), 11.1.111.44 (Android 2.x/3.x), 11.1.115.48 (Android 4.x); Adobe AIR/SDK/Compiler: 3.6.0.6090

  1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click context menu
  2. Identify the installed Adobe AIR version by checking the application's properties or help menu
  3. For Flash Player on Windows/Mac: Upgrade to version 11.6.602.180 or later (or 10.3.183.68 for Flash Player 10.x)
  4. For Flash Player on Linux: Upgrade to version 11.2.202.275 or later (or 10.3.183.68 for Flash Player 10.x)
  5. For Flash Player on Android 2.x/3.x: Upgrade to version 11.1.111.44 or later
  6. For Flash Player on Android 4.x: Upgrade to version 11.1.115.48 or later
  7. For Adobe AIR: Upgrade to version 3.6.0.6090 or later
  8. For Adobe AIR SDK and Compiler: Upgrade to version 3.6.0.6090 or later
Caveat Adobe Flash Player and AIR updates typically do not introduce breaking changes, but legacy content relying on older runtime features may require testing

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0646 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