dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-3122

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 by leveraging an unspecified "type confusion," a different vulnerability than CVE-2015-3119, CVE-2015-3120, CVE-2015-3121, and CVE-2015-4433.

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

Adobe Flash Player and AIR contain a type confusion vulnerability that allows remote attackers to execute arbitrary code via unspecified vectors. This is a memory corruption issue where the software fails to properly validate object types, enabling attackers to overwrite memory and inject malicious code.

MitigationUpdate Adobe Flash Player to version 13.0.0.302, 18.0.0.203, or later (or 11.2.202.481 for Linux). For Adobe AIR, update to 18.0.0.180 or later. Alternatively, since Flash is end-of-life, remove/uninstall Flash Player entirely to eliminate the attack surface.

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 a browser and navigate to https://helpx.adobe.com/flash-player.html, or in Internet Explorer visit 'About Adobe Flash Player' via the Tools menu, or check the file properties of NPSWF32.dll (located in C:\Windows\System32\Macromed\Flash\) or Flash.ocx (in C:\Windows\System32\). Right-click the DLL, select Properties, and view the Version tab.
    Affected if The displayed version is any of the following: 13.0.0.289 or earlier, 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 Linux
    Locate the libflashplayer.so file (typically in /usr/lib/flash-plugin/, /usr/lib/mozilla/plugins/, or ~/.mozilla/plugins/). Run 'rpm -q flash-plugin' for RPM-based distributions or 'dpkg -l | grep flash' for Debian-based systems to retrieve the installed version.
    Affected if The installed version matches any of the versions listed in the affected list (13.x versions up to and including 13.0.0.289, or any of the specific 14.x, 15.x, or 16.x versions enumerated).
  3. Check Adobe AIR version on Windows
    Open Control Panel and navigate to Programs and Features (or Add/Remove Programs). Look for 'Adobe AIR' in the list of installed programs. The version will be displayed in the column labeled 'Version'. Alternatively, check the installation directory (typically C:\Program Files\Adobe\Adobe AIR\) and view the properties of the Adobe AIR application executable.
    Affected if The version shown is 18.0.0.144 or any earlier version (the affected range includes versions up to and including 18.0.0.144).
  4. Check Adobe AIR SDK version
    If you have Adobe AIR SDK installed, open a command prompt and navigate to the AIR SDK directory. Run 'adl -version' if the AIR Developer Tool (adl) is available, or locate the AIR SDK version file (often named VERSION or version.properties) in the SDK root folder. On Windows, the SDK is often found in C:\Program Files\Adobe\Adobe AIR SDK or a custom installation path.
    Affected if The SDK version is 18.0.0.144 or earlier.

You are affected if any installed instance of Adobe Flash Player, Adobe AIR, or Adobe AIR SDK matches the specific versions listed in the affected range 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 a release after 18.0.0.144
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.302, 18.0.0.203, or later (or 11.2.202.481 for Linux). For Adobe AIR, update to 18.0.0.180 or later. Alternatively, since Flash is end-of-life, remove/uninstall Flash Player entirely to eliminate the attack surface.

Recommended fix High confidence

Flash Player 13.0.0.302 (13.x branch) or 18.0.0.203 (14.x-18.x branch) or 11.2.202.481 (Linux); Adobe AIR 18.0.0.180

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the player or visiting adobe.com/software/flash/about
  2. 2. Identify the currently installed Adobe AIR version from the Windows Control Panel or macOS Applications folder
  3. 3. For Flash Player: Download the appropriate fixed version from adobe.com - Windows/OS X users need 13.0.0.302 or 18.0.0.203 depending on their branch; Linux users need 11.2.202.481
  4. 4. For Adobe AIR: Download and install version 18.0.0.180 or later from adobe.com/air
  5. 5. For Adobe AIR SDK/Compiler: Download and install version 18.0.0.180 or later from adobe.com/air/sdk or adobe.com/air/sdk-compiler
  6. 6. Restart any browsers and ensure Flash Player plugin is updated
  7. 7. Verify the installed version matches the fixed release to confirm successful remediation
Caveat Flash Player 18.x introduced new major features; ensure compatibility with any dependent applications before upgrading

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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