Flash PlayerApplication · Adobe

CVE-2014-0519

HIGH · 7.5 CVSS v2.0 Published 2014-05-14
Fix available
A fix is available. Upgrade to 11.2.202.359 / 13.0.0.111 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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.214 on Windows and OS X and before 11.2.202.359 on Linux, Adobe AIR SDK before 13.0.0.111, and Adobe AIR SDK & Compiler before 13.0.0.111 allow attackers to bypass intended access restrictions via unspecified vectors, a different vulnerability than CVE-2014-0517, CVE-2014-0518, and CVE-2014-0520.

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 SDK contain a security bypass vulnerability that allows attackers to circumvent intended access restrictions, potentially enabling unauthorized access to sensitive resources or functionality.

MitigationUpdate Adobe Flash Player to version 13.0.0.214 (Windows/OS X) or 11.2.202.359 (Linux), and update Adobe AIR SDK to version 13.0.0.111 or later to remediate this vulnerability.

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.214>= 11.0, < 11.2.202.359
Adobe AirApplication
Affected:< 13.0.0.111

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 Windows Control Panel > Programs and Features, or check the version in Internet Explorer by navigating to about:flash (or using a Flash version checker website), or check the file version of C:\Windows\System32\Macromed\Flash\pepflashplayer32.dll or NPSWF32.dll
    Affected if Installed version is 13.0.0.0 to 13.0.0.213, OR 11.0.0.0 to 11.2.202.358
  2. Check Adobe Flash Player version on macOS
    Open Finder > Go > Go to Folder > /Library/Application Support/Adobe/Flash Player/, or check the version via Safari by visiting a Flash version checker page, or check the file version of /Library/Internet Plug-Ins/Flash Player.plugin
    Affected if Installed version is 13.0.0.0 to 13.0.0.213, OR 11.0.0.0 to 11.2.202.358
  3. Check Adobe Flash Player version on Linux
    Check the version of the NPAPI plugin by entering 'about:plugins' in Firefox address bar, or run 'rpm -q flash-player' or 'dpkg -l flash-player' depending on package manager, or check the file version of /usr/lib/flash-plugin/libflashplayer.so
    Affected if Installed version is 11.0.0.0 to 11.2.202.358 (Linux is only affected in the 11.x branch for this CVE)
  4. Check Adobe AIR version
    Open Windows Control Panel > Programs and Features and look for Adobe AIR, or on macOS check /Applications/Adobe AIR Installer.app version info, or check the AIR runtime folder on Windows at C:\Program Files\Adobe\Adobe AIR\versions\ or on Mac at /Library/Application Support/Adobe AIR/
    Affected if Installed version is any version lower than 13.0.0.111

Your environment is affected if Adobe Flash Player version falls within 13.0.0.0-13.0.0.213 or 11.0.0.0-11.2.202.358, OR if Adobe AIR version is lower than 13.0.0.111.

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.

From vendor data
Upgrade available Upgrade to 11.2.202.359 / 13.0.0.111 / 13.0.0.214 or later
Fixed in 11.2.202.35913.0.0.11113.0.0.214
Interim mitigation

Update Adobe Flash Player to version 13.0.0.214 (Windows/OS X) or 11.2.202.359 (Linux), and update Adobe AIR SDK to version 13.0.0.111 or later to remediate this vulnerability.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-0519 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