dbcve.org
Flash PlayerApplication · Adobe

CVE-2014-0576

HIGH · 10.0 CVSS v2.0 Published 2014-11-11
Fix available
A fix is available. Upgrade to 11.2.202.418 / 13.0.0.252 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.252 and 14.x and 15.x before 15.0.0.223 on Windows and OS X and before 11.2.202.418 on Linux, Adobe AIR before 15.0.0.356, Adobe AIR SDK before 15.0.0.356, and Adobe AIR SDK & Compiler before 15.0.0.356 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2014-0581, CVE-2014-8440, and CVE-2014-8441.

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

Memory corruption vulnerability in Adobe Flash Player and AIR allowing arbitrary code execution or denial of service via unspecified vectors. The flaw affects specific versions across Windows, OS X, and Linux platforms before the listed patched versions.

MitigationUpdate Adobe Flash Player to version 13.0.0.252, 15.0.0.223, or 11.2.202.418 (platform-dependent), and Adobe AIR to 15.0.0.356 or later to remediate.

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, < 13.0.0.252>= 14.0, <= 14.0.0.179>= 15.0, < 15.0.0.223>= 11.0, < 11.2.202.418
Air SdkApplication
Affected:<= 15.0.0.356
AirApplication
Affected:<= 15.0.0.356
Air Sdk \& CompilerApplication
Affected:< 15.0.0.356

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. Identify installed Adobe Flash Player version
    Open a web browser and navigate to 'about:plugins' or 'chrome://plugins' to view installed plugins. Alternatively, on Windows locate the Flash Player DLL file (npswf32.dll or Flash32_*.dll) in the browser's plugins folder or system directories, right-click the file, select Properties, and check the Version tab. On macOS, check /Library/Internet Plug-Ins/ or ~/Library/Internet Plug-Ins/ for the Flash Player plugin bundle and view its Info.plist for the version.
    Affected if The installed version is 13.0.0.0 or higher but lower than 13.0.0.252, OR 14.0.0.0 through 14.0.0.179, OR 15.0.0.0 through 15.0.0.222, OR 11.0.0.0 through 11.2.202.417.
  2. Identify installed Adobe AIR runtime version
    On Windows, open Programs and Features (or Add/Remove Programs) and locate Adobe AIR in the installed programs list to see the version. Alternatively, navigate to C:\Program Files (x86)\Adobe\Adobe AIR\Versions\ and check the folder name or view the version within the AIR application files. On macOS, check /Applications/Adobe AIR Installer.app or the Versions folder within the Adobe AIR application bundle.
    Affected if The installed Adobe AIR version is 15.0.0.356 or earlier.
  3. Identify installed Adobe AIR SDK version
    Locate the AIR SDK installation directory. On Windows, this is typically under the Adobe Flash Builder or Flex SDK installation path, or a standalone AIR SDK folder. Within that directory, open the AIR SDK Readme.txt or the release notes file which contains the SDK version number. Alternatively, check the 'sdk' folder metadata or version file included with the SDK.
    Affected if The installed Adobe AIR SDK version is lower than 15.0.0.356.

A system is affected if Adobe Flash Player version falls within any of the vulnerable ranges, or if Adobe AIR (runtime or SDK) version is at or below 15.0.0.356.

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.418 / 13.0.0.252 / 15.0.0.223 or later
Fixed in 11.2.202.41813.0.0.25215.0.0.223
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.252, 15.0.0.223, or 11.2.202.418 (platform-dependent), and Adobe AIR to 15.0.0.356 or later to remediate.

Recommended fix High confidence

Flash Player: 13.0.0.252, 14.0.0.180, 15.0.0.223, or 11.2.202.418 (Linux); Adobe AIR/SDK/Compiler: 15.0.0.356

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click context menu or visiting the version check page at about:plugins
  2. 2. Identify the currently installed Adobe AIR version via Windows Programs and Features or the AIR Settings
  3. 3. Navigate to the official Adobe security bulletin APSB14-24 at helpx.adobe.com/security/products/flash-player/apsb14-24.html
  4. 4. Download the appropriate fixed version for your platform (Windows, Mac, or Linux): Flash Player 13.0.0.252 (13.x branch), 14.0.0.180 (14.x branch), 15.0.0.223 (15.x branch), or 11.2.202.418 (Linux 11.2.x branch)
  5. 5. For Adobe AIR, download version 15.0.0.356
  6. 6. Uninstall the current vulnerable Flash Player and/or AIR version via Control Panel > Programs and Features
  7. 7. Restart the browser completely after uninstallation
  8. 8. Install the downloaded fixed version of Flash Player and/or AIR
Caveat None documented for this security patch; however, some older content relying on deprecated Flash features may require testing

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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