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 4 May 2022.
Flash PlayerApplication · Adobe

CVE-2015-0313

CRITICAL · 9.8 CVSS v3.1 Published 2015-02-02
Fix available
A fix is available. Upgrade to 11.2.202.442 / 13.0.0.269 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS 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.269 and 14.x through 16.x before 16.0.0.305 on Windows and OS X and before 11.2.202.442 on Linux allows remote attackers to execute arbitrary code via unspecified vectors, as exploited in the wild in February 2015, a different vulnerability than CVE-2015-0315, CVE-2015-0320, and CVE-2015-0322.

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 allowing remote attackers to execute arbitrary code via unspecified vectors. Actively exploited in the wild in February 2015. Affects versions before 13.0.0.269 (Windows/OS X), 14.x-16.x before 16.0.0.305 (Windows/OS X), and before 11.2.202.442 (Linux).

MitigationUpgrade Adobe Flash Player to version 13.0.0.269 or later (Windows/OS X) or 11.2.202.442 or later (Linux). If Flash is not required, remove or disable it 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:< 11.2.202.442< 13.0.0.269>= 14.0.0.125, < 16.0.0.305
EvergreenOperating system
Affected:= 11.4
OpensuseOperating system
Affected:= 13.1= 13.2
Linux Enterprise DesktopOperating system
Affected:= 11= 12
Linux Enterprise Workstation ExtensionOperating system
Affected:= 12
Internet ExplorerApplication
Affected:= 10= 11
EdgeWeb browser
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Check Adobe Flash Player version on Windows
    Open a browser with Flash, navigate to 'About Adobe Flash Player' (right-click on Flash content), or check the version via the Windows registry at HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion, or inspect the Flash DLL file (flash*.ocx) properties in System32
    Affected if The version is less than 11.2.202.442, OR less than 13.0.0.269, OR greater than or equal to 14.0.0.125 but less than 16.0.0.305
  2. Check Adobe Flash Player version on Linux
    Run 'rpm -q flash-player' or 'dpkg -l | grep flash' depending on package manager, or check /usr/lib/flash-player/ for the installed files
    Affected if The version is less than 11.2.202.442
  3. Check if Flash is enabled in Internet Explorer 10 or 11
    Open IE, go to Internet Options > Programs > Manage add-ons; verify if 'Shockwave Flash Object' is enabled, or check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility for Flash CLSIDs
    Affected if Flash is enabled in IE 10 or 11 and the player version is vulnerable per the version checks above
  4. Check if Flash is enabled in Microsoft Edge
    Open Edge, go to Settings > View advanced settings, verify the 'Enable Adobe Flash' toggle status; this can also be checked via registry at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\AllowFlash or HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\Edge\Capabilities
    Affected if Flash is enabled in Edge and the player version is vulnerable per the version checks above

You are affected if Adobe Flash Player is installed with a version matching the vulnerable ranges AND is enabled in any affected browser (IE 10/11 or Edge on Windows).

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.442 / 13.0.0.269 / 16.0.0.305 or later
Fixed in 11.2.202.44213.0.0.26916.0.0.305
Vendor patch technet.microsoft.com →
Interim mitigation

Upgrade Adobe Flash Player to version 13.0.0.269 or later (Windows/OS X) or 11.2.202.442 or later (Linux). If Flash is not required, remove or disable it to eliminate the attack surface.

Recommended fix High confidence

Flash Player 13.0.0.269 (or 16.0.0.305 for versions 14.x-16.x) on Windows/OS X; Flash Player 11.2.202.442 on Linux

  1. Identify all browsers and applications with Adobe Flash Player installed on the system
  2. Check the current Flash Player version by visiting Adobe's version check page or checking the About panel in each browser
  3. Download the fixed Flash Player version from the official Adobe Flash Player download page: https://get.adobe.com/flashplayer/
  4. For Windows and OS X: Upgrade to Flash Player 13.0.0.269 or 16.0.0.305 (or later) depending on the major version line
  5. For Linux: Upgrade to Flash Player 11.2.202.442 or later
  6. Ensure each affected browser (Internet Explorer, Edge, Firefox, Chrome) is updated with the new Flash Player version
  7. Restart all browsers after updating
  8. Consider enabling 'Notify me to install Adobe Flash Player updates' in the Flash Player settings or configuring automatic updates
Caveat Flash Player reached end-of-life on December 31, 2020; consider migrating away from Flash-based content as Adobe no longer provides security updates

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

Fix this in Flash Player Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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