dbcve.org
Flash PlayerApplication · Adobe

CVE-2015-3077

HIGH · 10.0 CVSS v2.0 Published 2015-05-13
Fix available
A fix is available. Upgrade to after 17.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.289 and 14.x through 17.x before 17.0.0.188 on Windows and OS X and before 11.2.202.460 on Linux, Adobe AIR before 17.0.0.172, Adobe AIR SDK before 17.0.0.172, and Adobe AIR SDK & Compiler before 17.0.0.172 allow attackers to execute arbitrary code by leveraging an unspecified "type confusion," a different vulnerability than CVE-2015-3084 and CVE-2015-3086.

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

A type confusion vulnerability in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code by exploiting improper type handling. The vulnerability affects specific versions across Windows, OS X, and Linux platforms.

MitigationUpdate Adobe Flash Player to version 13.0.0.289, 17.0.0.188, or 11.2.202.460 (depending on platform) and Adobe AIR to 17.0.0.172 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:<= 11.2.202.475<= 13.0.0.264= 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
AirApplication
Affected:<= 17.0.0.144
Air SdkApplication
Affected:<= 17.0.0.144
Air Sdk \& CompilerApplication
Affected:<= 17.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 a command prompt and run: reg query "HKLM\SOFTWARE\Macromedia\FlashPlayer" /v Version (for system-wide) or reg query "HKCU\SOFTWARE\Macromedia\FlashPlayer" /v Version (for user-specific). Alternatively, visit any website using Flash and check the version through the Adobe Flash Player Settings manager or type 'about:flash' in Internet Explorer.
    Affected if The installed version is <= 11.2.202.475, <= 13.0.0.264, or one of: 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
  2. Check Adobe Flash Player version on macOS or Linux
    On macOS, check via Safari by visiting a Flash-enabled site or check /Library/Application Support/Adobe/Flash Player/ for the version file. On Linux, check the installed package version using the package manager: dpkg -l | grep flashplugin (Debian/Ubuntu) or rpm -q flash-plugin (RHEL/CentOS).
    Affected if The installed version is <= 11.2.202.475, <= 13.0.0.264, or one of: 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
  3. Check Adobe AIR version
    On Windows, open Add or Remove Programs and look for Adobe AIR, or check the registry key HKLM\SOFTWARE\Adobe\AIR\Version. On macOS, check /Library/Application Support/Adobe/AIR/Versions/ or run: defaults read /Applications/Adobe\ AIR\Application/Contents/Info CFBundleVersion.
    Affected if The installed version is <= 17.0.0.144
  4. Check Adobe AIR SDK version
    If you are a developer using the AIR SDK, check the version file typically located at AIR_SDK_README.txt or the version.properties file within the SDK directory, or run: adt -version if the AIR Developer Tool is in your PATH.
    Affected if The installed SDK version is <= 17.0.0.144

A user is affected if Adobe Flash Player version is within the affected ranges listed, or Adobe AIR/AIR SDK version is <= 17.0.0.144, and the vulnerable Flash Player or AIR component is enabled or installed.

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 17.0.0.144
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.289, 17.0.0.188, or 11.2.202.460 (depending on platform) and Adobe AIR to 17.0.0.172 or later.

Recommended fix High confidence

Flash Player 17.0.0.188 (Windows/OS X), 13.0.0.289 (13.x branch), 11.2.202.460 (Linux); Adobe AIR 17.0.0.172; Adobe AIR SDK 17.0.0.172

  1. 1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click context menu or visiting https://helpx.adobe.com/flash-player.html
  2. 2. Identify the installed Adobe AIR version from Add/Remove Programs (Windows) or by running 'airdiag' or checking the application directory (macOS/Linux)
  3. 3. For Windows/OS X users: Download Flash Player 17.0.0.188 or later from the official Adobe download page at https://get.adobe.com/flashplayer/
  4. 4. For Linux users: Download Flash Player 11.2.202.460 or later from the Adobe Linux download page
  5. 5. For Adobe AIR users: Download AIR 17.0.0.172 or later from https://get.adobe.com/air/
  6. 6. For Adobe AIR SDK developers: Download AIR SDK 17.0.0.172 or later from https://helpx.adobe.com/air-sdk/download.html
  7. 7. Close all web browsers and applications using Flash Player before running the installer
  8. 8. Run the installer with administrator privileges and follow the prompts
Caveat Upgrading Flash Player may cause compatibility issues with older web content; some legacy websites may require older plugin versions

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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