dbcve.org
Flash PlayerApplication · Adobe

CVE-2013-1370

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-1369, 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 allowing attackers to execute arbitrary code via unspecified vectors. Affects multiple versions across Windows, Mac OS X, Linux, and Android platforms.

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), and Adobe AIR to 3.6.0.597+ (runtime) or 3.6.0.599+ (SDK).

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 in browsers
    Open a browser and navigate to 'about:plugins' (Firefox) or chrome://plugins (Chrome) to locate the Flash Player plugin and note its version. Alternatively, visit Adobe's version check page at get.adobe.com/flashplayer/about/
    Affected if The displayed version matches any of these ranges: 10.3.x before 10.3.183.63 (Windows), 11.6.x before 11.6.602.168 (Windows), 10.3.x before 10.3.183.61 (Mac), 11.2.x before 11.2.202.270 (Linux), 11.1.x before 11.1.111.43 (Android 2.x/3.x), or 11.1.x before 11.1.115.47 (Android 4.x)
  2. Check Adobe Flash Player version on Windows
    Open Control Panel and navigate to 'Programs and Features' (or 'Add or Remove Programs'), then look for 'Adobe Flash Player XX' in the list of installed software to see the version.
    Affected if The installed version is listed as any version below 10.3.183.63 or 11.6.602.168 for Windows Flash Player
  3. Check Adobe AIR runtime version
    On Windows, open Control Panel and check 'Programs and Features' for 'Adobe AIR'. On Mac, open Finder, go to /Applications, and check for Adobe AIR. Note the version displayed.
    Affected if The installed Adobe AIR runtime version is lower than 3.6.0.597
  4. Check Adobe AIR SDK version
    Look for the Adobe AIR SDK installation directory. On Windows, common paths are C:\Program Files\Adobe\AIR SDK or C:\Users\<user>\AppData\Local\Adobe\AIR\SDK. On Mac, check /usr/local/AIR_SDK or ~/Developer/SDKs/AIR. Check the SDK's readme or version file.
    Affected if The installed Adobe AIR SDK version is lower than 3.6.0.599

You are affected if Adobe Flash Player, Adobe AIR runtime, or Adobe AIR SDK is installed with a version lower than the minimum fixed versions listed for your platform.

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), and Adobe AIR to 3.6.0.597+ (runtime) or 3.6.0.599+ (SDK).

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 which Adobe Flash Player version is currently installed by navigating to 'About Flash Player' in the context menu or visiting adobe.com/software/flash/about
  2. Download the appropriate fixed version from adobe.com based on your platform: Windows 10.3.183.63 or 11.6.602.168, Mac OS X 10.3.183.61 or 11.6.602.167, Linux 10.3.183.61 or 11.2.202.270
  3. Close all browser instances that may be running Flash Player
  4. Install the updated Flash Player version matching your platform and existing major version branch
  5. For Adobe AIR users, download and install AIR version 3.6.0.597 or later from adobe.com
  6. For AIR SDK developers, update to AIR SDK version 3.6.0.599 or later
  7. Verify the installed version matches the fixed release numbers specified
  8. Consider migrating away from Flash Player as Adobe ended support in December 2020 - evaluate HTML5 alternatives for any remaining Flash-dependent applications
Caveat Flash Player reached end-of-life in December 2020 and no longer receives security updates; migrating to HTML5-based alternatives is strongly recommended for long-term security

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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