Flash PlayerApplication · Adobe

CVE-2015-3124

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
Public exploit 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
Use-after-free vulnerability in 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 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-3118, CVE-2015-3127, CVE-2015-3128, CVE-2015-3129, CVE-2015-3131, CVE-2015-3132, CVE-2015-3136, CVE-2015-3137, CVE-2015-4428, CVE-2015-4430, and CVE-2015-5117.

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

Use-after-free vulnerability in Adobe Flash Player and AIR allows remote attackers to execute arbitrary code via unspecified vectors. The flaw occurs when memory is accessed after being freed, potentially enabling complete system compromise.

MitigationUpdate Adobe Flash Player to version 13.0.0.302 or later (14.x/18.x to 18.0.0.203+), and Adobe AIR to 18.0.0.180 or later. For Linux, update to 11.2.202.481 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 in Windows browsers
    Open any browser and navigate to 'About Adobe Flash Player' (or right-click on Flash content and select 'About Adobe Flash Player'), or visit https://helpx.adobe.com/flash-player.html to detect the installed version via the browser.
    Affected if The displayed version is 13.0.0.289 or earlier, any 14.x version listed (14.0.0.125/145/176/179), any 15.x version listed (15.0.0.152/167/189/223/239/246), or 16.0.0.235.
  2. Check Adobe Flash Player version in Linux browsers
    Open a terminal and run: 'dpkg -l | grep flash' (Debian/Ubuntu) or 'rpm -qa | grep flash' (Red Hat/CentOS) to list installed Flash packages, or check the browser's plugin information page.
    Affected if The installed Flash Player version for Linux is 11.2.202.480 or earlier.
  3. Check Adobe AIR desktop runtime version
    On Windows, open 'Add or Remove Programs' and look for 'Adobe AIR', or on macOS check '/Applications/Utilities/Adobe AIR Installation.app'. The version is typically displayed in the application entry or can be found in the AIR application folder metadata.
    Affected if The installed Adobe AIR version is 18.0.0.144 or earlier.
  4. Check Adobe AIR SDK version
    Locate the AIR SDK installation directory (commonly at 'C:\Program Files (x86)\Adobe\Adobe AIR SDK' on Windows or '/opt/air-sdk' on Linux/Mac). Open the 'VERSION' or 'readme.txt' file within the SDK folder, which contains the exact version number.
    Affected if The AIR SDK version is 18.0.0.144 or earlier.
  5. Check Adobe AIR SDK Compiler version
    Look for the AIR SDK Compiler (airc) in the SDK installation under 'lib/aac' or check the compiler's version by running 'airc -version' from the command line within the SDK bin directory.
    Affected if The AIR SDK Compiler version corresponds to an SDK version of 18.0.0.144 or earlier.

A user is affected if Adobe Flash Player is any of the versions listed (13.0.0.289 or lower, specific 14.x/15.x/16.x versions), or if Adobe AIR/AIR SDK/AIR SDK Compiler is version 18.0.0.144 or earlier.

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 or later (14.x/18.x to 18.0.0.203+), and Adobe AIR to 18.0.0.180 or later. For Linux, update to 11.2.202.481 or later.

Recommended fix High confidence

Flash Player 13.0.0.302+ or 18.0.0.203+ (Windows/OS X), 11.2.202.481+ (Linux); AIR 18.0.0.180+; AIR SDK 18.0.0.180+; AIR SDK & Compiler 18.0.0.180+

  1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click menu or checking the system's installed programs
  2. Identify the currently installed Adobe AIR version by checking the system's installed programs
  3. For Flash Player on Windows and OS X: Download and install version 18.0.0.203 or later from the Adobe Flash Player download page
  4. For Flash Player on Linux: Download and install version 11.2.202.481 or later from the Adobe Flash Player download page
  5. For Flash Player 13.x: Download and install version 13.0.0.302 or later
  6. For Adobe AIR: Download and install version 18.0.0.180 or later from the Adobe AIR download page
  7. For Adobe AIR SDK: Download and install version 18.0.0.180 or later from the Adobe AIR SDK download page
  8. For Adobe AIR SDK & Compiler: Download and install version 18.0.0.180 or later

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 / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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