dbcve.org
Flash PlayerApplication · Adobe

CVE-2013-1375

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
Heap-based buffer 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

Heap-based buffer overflow vulnerability in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code via unspecified vectors. The flaw exists in the processing of malicious content and enables complete system compromise.

MitigationUpdate Adobe Flash Player to version 10.3.183.68/11.6.602.180 (Windows/Mac), 11.2.202.275 (Linux), or 11.1.115.48 (Android); update Adobe AIR to 3.6.0.6090 or later. Consider removing Flash if unused.

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 if Adobe Flash Player is installed
    On Windows, open Add/Remove Programs or check for NPSWF32.dll in the system directory. On Mac, check /Library/Application Support/Adobe/Flash Player/ or /Users/[user]/Library/Application Support/Adobe/Flash Player/. On Android, check installed apps for Flash Player.
    Affected if Adobe Flash Player is present on the system
  2. Identify the installed Flash Player version
    On Windows, right-click the DLL or OCX file (usually in C:\Windows\System32\Macromed\Flash\) and view Properties > Details for version info. On Mac, check the version.plist file in the Flash Player folder. On Android, check the app info in Settings > Apps.
    Affected if The version number matches or falls within the affected ranges: any 11.x version from 11.0 through 11.6.602.171, or version 10.1.106.17, 10.2.157.51, or 10.3.186.7 on Android
  3. Check for Adobe AIR installation
    On Windows, look for Adobe AIR in Add/Remove Programs or check C:\Program Files\Adobe\Adobe AIR\. On Mac, check /Applications/Adobe AIR or /Users/[user]/Applications/. For Android, check installed apps for Adobe AIR.
    Affected if Adobe AIR is installed on the system
  4. Determine Adobe AIR version
    On Windows, right-click the Adobe AIR application file or its DLL and view Properties > Details for version. On Mac, right-click Adobe AIR.app and check Get Info. On Android, view the app info in Settings > Apps.
    Affected if The AIR version is 3.6.0.597 or earlier, or is 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, or 1.5.1.8210 (any AIR version is listed as affected in the provided data)
  5. Check Adobe AIR SDK or Compiler version if present
    If developing with AIR SDK, check the version.properties or AIR SDK version file in the SDK installation directory.
    Affected if The AIR SDK/Compiler version is 3.6.0.599 or earlier (SDK And Compiler), or 3.6.0.597 or earlier (Air Sdk), or specific versions 3.0.0.4080 through 3.5.0.1060 as listed in the affected products

If Adobe Flash Player version 11.x (through 11.6.602.171), certain 10.x versions on Android, or any Adobe AIR version 3.6.0.597 and below is installed, the system is potentially affected by this heap-based buffer overflow vulnerability.

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 version 10.3.183.68/11.6.602.180 (Windows/Mac), 11.2.202.275 (Linux), or 11.1.115.48 (Android); update Adobe AIR to 3.6.0.6090 or later. Consider removing Flash if unused.

Recommended fix High confidence

Flash Player 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 3.6.0.6090+; Adobe AIR SDK 3.6.0.6090+

  1. Identify the specific Adobe product installed (Flash Player, Flash Player for Android, Adobe AIR, or Adobe AIR SDK/Compiler)
  2. Identify the current version number of the installed product
  3. Determine the target platform (Windows, Mac OS X, Linux, or Android) and Android version for Flash Player
Caveat Flash Player reached end-of-life in December 2020; upgrading may require migrating to alternative technologies

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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