dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-3130

HIGH · 10.0 CVSS v2.0 Published 2015-07-09
Fix available
A fix is available. Upgrade to after 18.0.0.144 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Adobe Flash Player before 13.0.0.302 and 14.x through 18.x before 18.0.0.203 on Windows and OS X and before 11.2.202.481 on Linux, Adobe AIR before 18.0.0.180, Adobe AIR SDK before 18.0.0.180, and Adobe AIR SDK & Compiler before 18.0.0.180 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-3117, CVE-2015-3123, CVE-2015-3133, CVE-2015-3134, and CVE-2015-4431.

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

Memory corruption vulnerability in Adobe Flash Player and Adobe AIR allowing arbitrary code execution. Affects specific versions across Windows, OS X, and Linux platforms, as well as AIR SDK and Compiler components.

MitigationUpdate Adobe Flash Player to version 13.0.0.302 (Windows/OS X), 11.2.202.481 (Linux), or 18.0.0.203 (14.x-18.x). Update Adobe AIR and AIR SDK to version 18.0.0.180 or later.

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:<= 13.0.0.289= 14.0.0.125= 14.0.0.145= 14.0.0.176= 14.0.0.179= 15.0.0.152= 15.0.0.167= 15.0.0.189= 15.0.0.223= 15.0.0.239= 15.0.0.246= 16.0.0.235
AirApplication
Affected:<= 18.0.0.144
Air SdkApplication
Affected:<= 18.0.0.144
Air Sdk \& CompilerApplication
Affected:<= 18.0.0.144

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 Registry Editor and navigate to HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion, or check the file properties of Flash32_*.ocx in C:\Windows\System32\Macromed\Flash\
    Affected if The version value is 13.0.0.289 or earlier, or matches 14.0.0.125, 14.0.0.145, 14.0.0.176, 14.0.0.179, 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.239, 15.0.0.246, or 16.0.0.235
  2. Check Adobe Flash Player version on macOS or Linux
    On macOS, inspect /Library/Application Support/Adobe/Flash Player/ or the browser plugin file version. On Linux, check /usr/lib/flash-plugin/ or the browser plugin directory for the Flash Player library file and view its version property.
    Affected if The installed version matches any of the affected versions listed in the CVE (13.0.0.289 or earlier, or any of the specific 14.x, 15.x, or 16.x versions listed)
  3. Check Adobe AIR version
    On Windows, open Add or Remove Programs and look for Adobe AIR, or check the version in C:\Program Files\Adobe\Adobe AIR\ or C:\Program Files (x86)\Adobe\Adobe AIR\. On macOS, check /Applications/Adobe AIR/ or view the Adobe AIR.app Contents/Info.plist version.
    Affected if The Adobe AIR version is 18.0.0.144 or any earlier version
  4. Check Adobe AIR SDK version
    Look for the AIR SDK installation directory (commonly C:\Program Files (x86)\Adobe\Adobe AIR SDK or similar) and locate a version file or read the version from the SDK's readme or release notes, or check the AIR SDK bin directory for tooling that displays the SDK version.
    Affected if The AIR SDK or AIR SDK Compiler version is 18.0.0.144 or earlier

The environment is affected if any installed Adobe Flash Player, Adobe AIR, or Adobe AIR SDK version matches the specific versions or version ranges listed in the 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 a release after 18.0.0.144
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.302 (Windows/OS X), 11.2.202.481 (Linux), or 18.0.0.203 (14.x-18.x). Update Adobe AIR and AIR SDK to version 18.0.0.180 or later.

Recommended fix High confidence

Flash Player 13.0.0.302 (13.x branch), Flash Player 18.0.0.203 (14.x-18.x branch), Flash Player 11.2.202.481 (Linux), AIR 18.0.0.180, AIR SDK 18.0.0.180

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the context menu or visiting 'about:flash' in the browser
  2. 2. For Windows/OS X: If using Flash Player 13.x, upgrade to version 13.0.0.302; if using Flash Player 14.x-18.x, upgrade to version 18.0.0.203
  3. 3. For Linux: Upgrade to Flash Player version 11.2.202.481
  4. 4. For Adobe AIR: Upgrade to version 18.0.0.180
  5. 5. For Adobe AIR SDK: Upgrade to version 18.0.0.180
  6. 6. For Adobe AIR SDK & Compiler: Upgrade to version 18.0.0.180
  7. 7. Download the appropriate fixed version from the official Adobe security bulletin at https://helpx.adobe.com/security/products/flash-player/apsb15-16.html
  8. 8. Close all browser instances and applications using Flash Player before installing the update
Caveat Adobe Flash Player is now deprecated and no longer supported; consider migrating away from Flash-based content

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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