dbcve.org
Flash PlayerApplication · Adobe

CVE-2013-1369

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-1366, CVE-2013-1367, CVE-2013-1368, 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 in Adobe Flash Player and Adobe AIR allows attackers to execute arbitrary code via unspecified vectors. This is a memory corruption vulnerability in the Flash runtime that could be exploited through malicious SWF files or web content.

MitigationUpgrade to the patched versions of Adobe Flash Player (10.3.183.63+/11.6.602.168+ for Windows, 11.6.602.167+ for Mac, 11.2.202.270+ for Linux, 11.1.111.43+ for Android 2.x/3.x, 11.1.115.47+ for Android 4.x) and Adobe AIR (3.6.0.597+ / SDK 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. Check Adobe Flash Player version on Windows
    Open Control Panel > Programs and Features, look for Adobe Flash Player XX.X or run: flashplayerplugin_version in URL bar of IE, or check C:\Windows\System32\Macromed\Flash\Flash*.ocx properties
    Affected if Version is 10.3.x before 10.3.183.63, 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. Check Adobe Flash Player version on Mac
    Open /Library/Application Support/Adobe/Flash Player/ and look at the installed version, or check via System Preferences > Flash Player > Update
    Affected if Version is 10.3.x before 10.3.183.63, 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.167 (Mac)
  3. Check Adobe Flash Player version on Linux
    Run rpm -q flash-plugin or dpkg -l | grep flash in terminal, or visit about:plugin in Firefox
    Affected if Version is 11.2.x before 11.2.202.270 on Linux systems
  4. Check Adobe AIR version
    Open Control Panel > Programs and Features (Windows) or /Applications/Adobe AIR (Mac), or run: adl -version from AIR SDK bin directory
    Affected if Version is earlier than 3.6.0.597 for Adobe AIR runtime or earlier than 3.6.0.599 for Adobe AIR SDK
  5. Verify Flash plugin is active in browsers
    Type about:plugins in browser address bar, or check browser add-ons/plugin settings for 'Shockwave Flash'
    Affected if Flash plugin is present and enabled in any browser on the system

System is affected if any installed Adobe Flash Player or Adobe AIR version falls within the vulnerable ranges listed for this CVE.

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 to the patched versions of Adobe Flash Player (10.3.183.63+/11.6.602.168+ for Windows, 11.6.602.167+ for Mac, 11.2.202.270+ for Linux, 11.1.111.43+ for Android 2.x/3.x, 11.1.115.47+ for Android 4.x) and Adobe AIR (3.6.0.597+ / SDK 3.6.0.599+).

Recommended fix High confidence

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.x/3.x), 11.1.115.47+ (Android 4.x); AIR 3.6.0.597+; AIR SDK 3.6.0.599+

  1. Identify the currently installed version of Adobe Flash Player and/or AIR on the system
  2. Access the Adobe Flash Player download page at get.adobe.com/flashplayer or the Adobe AIR download page
  3. Download the appropriate fixed version based on your platform: Windows users need 10.3.183.63 or 11.6.602.168+, Mac OS X users need 10.3.183.61 or 11.6.602.167+, Linux users need 10.3.183.61 or 11.2.202.270+
  4. For Android devices: download 11.1.111.43+ for Android 2.x/3.x or 11.1.115.47+ for Android 4.x
  5. For Adobe AIR: download version 3.6.0.597 or higher
  6. For Adobe AIR SDK: download version 3.6.0.599 or higher
  7. Uninstall the current version of Flash Player and/or AIR from the system
  8. Install the newly downloaded fixed version
Caveat Adobe Flash is deprecated and reaching end-of-life; some older Flash content may not function on newer versions or modern browsers

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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