dbcve.org
Flash PlayerApplication · Adobe

CVE-2013-0639

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
Integer overflow 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.

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 allows remote attackers to execute arbitrary code via unspecified vectors. The overflow occurs when the software handles specially crafted content, leading to heap corruption and potential code execution.

MitigationUpdate Adobe Flash Player to version 11.6.602.168 (Windows) / 11.6.602.167 (Mac) / 11.2.202.270 (Linux) or later, and Adobe AIR to 3.6.0.597 or later. Remove or disable Flash Player where possible given its end-of-life status.

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 Flash Player version on Windows
    Check the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\Version or examine the file properties of the Flash Player plugin (NPSWF32.dll or Flash32_*.ocx) typically located in C:\Windows\System32\Macromed\Flash or browser plugin directories
    Affected if The detected version is 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/11.6.602.167
  2. Identify installed Flash Player version on Mac
    Check the file version of /Library/Application Support/Adobe/Flash Player/ or browser plugin locations in ~/Library/Application Support/Google/Chrome/Default/Plugins/ or equivalent browser plugin directories
    Affected if The detected version matches the Windows-affected ranges listed above (note Mac uses 11.6.602.167 as the fixed version threshold)
  3. Identify installed Flash Player version on Linux
    Use the command 'rpm -q flash-plugin' or 'dpkg -l flashplugin-installer' to query the package, or check the file version of /usr/lib/flash-plugin/ or /usr/lib/mozilla/plugins/flashplayer.so
    Affected if The detected version is 11.2.x before 11.2.202.270 (Linux only had 11.2.x releases)
  4. Identify installed Adobe AIR version
    On Windows, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR or examine the file version of C:\Program Files\Adobe\Adobe AIR\Versions\1.0\Adobe AIR.dll; on Mac check /Applications/Adobe AIR.app/Contents/Info.plist
    Affected if The detected version is earlier than 3.6.0.597
  5. Identify installed Adobe AIR SDK version
    Check the SDK version file in the installed Adobe AIR SDK directory, typically found via 'air -version' command if SDK is in PATH, or by examining the file version of AIR SDK bin files
    Affected if The detected SDK version is earlier than 3.6.0.599
  6. Determine if Flash Player is actively enabled
    Check browser settings or system configuration where Flash content is allowed to load; on Windows also verify if the Flash ActiveX control (Flash10ax.ocx) is registered and enabled in Internet Explorer
    Affected if Flash Player versions in the affected ranges are installed AND the software is enabled (even if not actively used, the vulnerable code is present on the system)

A system is affected if any installed Adobe Flash Player version falls within 10.3.x before 10.3.183.63/10.3.183.61, 11.1.x before 11.1.111.43/11.1.115.47, 11.2.x before 11.2.202.270, or 11.6.x before 11.6.602.168/11.6.602.167; OR if Adobe AIR is earlier than 3.6.0.597; OR if Adobe AIR SDK is earlier than 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 version 11.6.602.168 (Windows) / 11.6.602.167 (Mac) / 11.2.202.270 (Linux) or later, and Adobe AIR to 3.6.0.597 or later. Remove or disable Flash Player where possible given its end-of-life status.

Recommended fix High confidence

Adobe Flash Player 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); Adobe AIR 3.6.0.597+; Adobe AIR SDK 3.6.0.599+

  1. 1. Identify the currently installed Adobe Flash Player or AIR version by checking About or using the version checker at adobe.com/software/flash/about/
  2. 2. Download the appropriate fixed version from adobe.com: Flash Player 10.3.183.63+ (Windows), 10.3.183.61+ (Mac), 10.3.183.61+ or 11.2.202.270+ (Linux), 11.1.111.43+ (Android 2.x/3.x), 11.1.115.47+ (Android 4.x)
  3. 3. Download Adobe AIR 3.6.0.597 or later, or AIR SDK 3.6.0.599 or later if using the SDK
  4. 4. Close all browsers and applications that use Flash Player or AIR
  5. 5. Run the installer for the updated version
  6. 6. Verify the update was successful by checking the version again
Caveat Flash Player reached end-of-life on December 31, 2020; consider migrating to HTML5 or removing Flash entirely rather than applying this legacy update

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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