dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Jun 2022.
Flash PlayerApplication · Adobe

CVE-2015-0310

HIGH · 7.8 CVSS v3.1 Published 2015-01-23
Fix available
A fix is available. Upgrade to 11.2.202.438 / 13.0.0.262 or later.
See remediation →
97/100
Remediation priority · Urgent
In the wild No privileges 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.262 and 14.x through 16.x before 16.0.0.287 on Windows and OS X and before 11.2.202.438 on Linux does not properly restrict discovery of memory addresses, which allows attackers to bypass the ASLR protection mechanism on Windows, and have an unspecified impact on other platforms, via unknown vectors, as exploited in the wild in January 2015.

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 contains a memory address disclosure vulnerability that fails to properly restrict discovery of memory addresses, allowing attackers to bypass the ASLR (Address Space Layout Randomization) protection mechanism. This information disclosure was actively exploited in the wild in January 2015.

MitigationUpgrade Adobe Flash Player to version 13.0.0.262 or later for the 13.x branch, 16.0.0.287 or later for 14.x-16.x branches on Windows/OS X, or 11.2.202.438 or later on Linux. Alternatively, remove Flash Player if unnecessary.

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.438< 13.0.0.262>= 14.0, < 16.0.0.287

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Verify Adobe Flash Player is installed
    Check for Flash Player in browsers (Internet Explorer, Firefox, Chrome) or as a standalone plugin. On Windows, look in C:\Windows\System32\Macromed\Flash or browser plugin directories. On macOS, check /Library/Internet Plug-Ins/ or ~/Library/Internet Plug-Ins/. On Linux, check /usr/lib/flash-plugin/ or /usr/lib64/flash-plugin/.
    Affected if Flash Player is not present on the system (not affected)
  2. Determine installed Flash Player version in Internet Explorer
    Open Internet Explorer, navigate to http://www.adobe.com/software/flash/about/, or go to Manage Add-ons and look for the Shockwave Flash Object version.
    Affected if Version displayed is less than 11.2.202.438, or between 13.0.0.0 and 13.0.0.261, or between 14.0.0.0 and 16.0.0.286
  3. Determine installed Flash Player version in other browsers
    In Firefox, go to Add-ons > Plugins and check Shockwave Flash. In Chrome, type chrome://plugins in the address bar and find Flash. On Linux, run rpm -q flash-player or dpkg -l | grep flash, or check the version file in the Flash installation directory.
    Affected if Version displayed is less than 11.2.202.438, or between 13.0.0.0 and 13.0.0.261, or between 14.0.0.0 and 16.0.0.286
  4. Verify if Flash is enabled in the browser
    In each browser, go to the plugins/add-ons settings and confirm that the Flash plugin is set to 'Always Activate' or 'Enabled'. For Internet Explorer, check Manage Add-ons for the Shockwave Flash Object.
    Affected if Flash Player is installed with a vulnerable version AND is enabled in any browser

A user is affected if Adobe Flash Player is installed and enabled with a version less than 11.2.202.438, 13.0.0.0-13.0.0.261, or 14.0.0.0-16.0.0.286.

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 11.2.202.438 / 13.0.0.262 / 16.0.0.287 or later
Fixed in 11.2.202.43813.0.0.26216.0.0.287
Vendor patch helpx.adobe.com →
Interim mitigation

Upgrade Adobe Flash Player to version 13.0.0.262 or later for the 13.x branch, 16.0.0.287 or later for 14.x-16.x branches on Windows/OS X, or 11.2.202.438 or later on Linux. Alternatively, remove Flash Player if unnecessary.

Recommended fix High confidence

Upgrade to Flash Player 16.0.0.287 (for 14.x-16.x on Windows/macOS), 13.0.0.262 (for 13.x on Windows/macOS), or 11.2.202.438 (for Linux)

  1. Verify current Flash Player version by navigating to 'about:flash' in a browser or checking 'Add or Remove Programs'
  2. For Windows: Download the appropriate installer from the official Adobe Flash Player download page (get.adobe.com/flashplayer) matching your system architecture (32-bit or 64-bit)
  3. For macOS: Download the .dmg installer from the official Adobe Flash Player download page
  4. For Linux: Download the .rpm or .deb package from the Adobe Flash Player Linux repository or get.adobe.com/flashplayer
  5. Close all web browsers that may be using Flash Player
  6. Run the downloaded installer with administrator/root privileges
  7. Restart the browser after installation completes
  8. Verify the updated version by checking 'about:flash' or the Flash Player About dialog
Caveat Flash Player is 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 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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