Flash PlayerApplication · Adobe

CVE-2013-1366

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
Buffer 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, a different vulnerability than CVE-2013-0642, CVE-2013-0645, CVE-2013-1365, CVE-2013-1367, CVE-2013-1368, CVE-2013-1369, CVE-2013-1370, CVE-2013-1372, and CVE-2013-1373.

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

Buffer overflow vulnerability in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code via unspecified vectors. The flaw affects multiple platforms (Windows, Mac OS X, Linux, Android) and is distinct from related CVEs fixed in the same security bulletin.

MitigationUpdate 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), 11.1.115.47+ (Android 4.x); update Adobe AIR to 3.6.0.597+ and AIR SDK to 3.6.0.599+. Remove unused Flash installations where possible.

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, check registry key HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion or HKLM\SOFTWARE\WOW6432Node\Macromedia\FlashPlayer. On Mac, check /Library/Application Support/Adobe/Flash Player/installed.cfg or System Preferences. On Linux, run 'rpm -q flash-plugin' or 'dpkg -l | grep flash' or check /usr/lib/flash-plugin. Alternatively, open a browser and navigate to about:flash or visit Adobe's version check page.
    Affected if The installed version falls within: 10.3.x before 10.3.183.63; 11.6.x before 11.6.602.168 (Windows) or before 11.6.602.167 (Mac); 11.2.x before 11.2.202.270 (Linux); 11.1.x before 11.1.111.43 (Android 2.x/3.x) or before 11.1.115.47 (Android 4.x)
  2. Identify installed Adobe AIR version
    On Windows, open Programs and Features or check registry HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR. On Mac, check /Applications/Adobe AIR or run 'defaults read /Applications/Adobe AIR.app/Contents/Info CFBundleVersion'. On Linux, run 'rpm -q adobe-air' or check /opt/adobe-air.
    Affected if The installed version is lower than 3.6.0.597
  3. Identify installed Adobe AIR SDK version
    Check the SDK version file in the AIR SDK installation directory, typically named VERSION or manifest.xml, or run 'air-sdk-version' if available in the SDK bin folder.
    Affected if The installed SDK version is lower than 3.6.0.599
  4. Confirm the vulnerability applies only to running instances
    Verify that the Flash Player browser plugin or Adobe AIR application is actively in use. On Windows, check running processes for plugin-container.exe (Firefox) or Flash*.dll loaded in browsers. On Mac, check Activity Monitor for Flash Player processes.
    Affected if The vulnerable version is installed AND the Flash plugin or AIR application is enabled or actively running in any browser or desktop environment

A system is affected if Adobe Flash Player version 10.3.x, 11.1.x, 11.2.x, or 11.6.x below the fixed thresholds, or Adobe AIR below 3.6.0.597, or Adobe AIR SDK below 3.6.0.599 is installed and actively in use.

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 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), 11.1.115.47+ (Android 4.x); update Adobe AIR to 3.6.0.597+ and AIR SDK to 3.6.0.599+. Remove unused Flash installations where possible.

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), 11.1.111.43 (Android 2/3), 11.1.115.47 (Android 4); Adobe AIR 3.6.0.597; AIR SDK 3.6.0.599

  1. Identify the current Adobe Flash Player or AIR version installed on the system
  2. Based on the operating system, upgrade to the fixed version: For Windows Flash Player, upgrade to 10.3.183.63 or 11.6.602.168 or later; For Mac OS X Flash Player, upgrade to 10.3.183.61 or 11.6.602.167 or later; For Linux Flash Player, upgrade to 10.3.183.61 or 11.2.202.270 or later; For Android 2.x/3.x Flash Player, upgrade to 11.1.111.43 or later; For Android 4.x Flash Player, upgrade to 11.1.11
  3. Verify the version after upgrade to confirm the patch was applied

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-1366 — 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-1366 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