CVE-2014-0517
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 · uneditedAdobe 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-0518, CVE-2014-0519, 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 · moderate confidenceAdobe Flash Player and AIR SDK contain a security bypass vulnerability that allows attackers to circumvent intended access restrictions. The vulnerability affects specific versions prior to 13.0.0.214 (Flash Player on Windows/OS X), 11.2.202.359 (Flash Player on Linux), and 13.0.0.111 (AIR SDK). The specific attack vectors are not detailed in the advisory.
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>= 13.0, < 13.0.0.214>= 11.0, < 11.2.202.359< 13.0.0.111CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe Flash Player version on WindowsOpen a web browser and navigate to any Flash-based content, then right-click and select 'About Adobe Flash Player', or open Control Panel and look for 'Programs and Features' to find the installed Flash versionAffected if The version listed is 13.0.x (where x is less than 214) or 11.0.x through 11.2.202.358 on Windows
-
Identify installed Adobe Flash Player version on macOSOpen a web browser and navigate to any Flash-based content, then right-click and select 'About Adobe Flash Player', or check the Applications folder for Flash Player installer versionsAffected if The version listed is 13.0.x (where x is less than 214) or 11.0.x through 11.2.202.358 on macOS
-
Identify installed Adobe Flash Player version on LinuxOpen a web browser with Flash support and navigate to any Flash content, then right-click and select 'About Adobe Flash Player', or run 'rpm -q flash-plugin' or 'dpkg -l' commands depending on your package managerAffected if The version listed is between 11.0 and 11.2.202.358 inclusive on Linux
-
Identify installed Adobe AIR versionCheck your system for Adobe AIR installation - on Windows look in 'Programs and Features', on macOS check the Applications folder, or run 'air -version' from command line if AIR SDK is installedAffected if The version is less than 13.0.0.111 or the version cannot be determined but AIR is present on a system that has not been updated since 2014
-
Check for active browser pluginsIn each installed web browser (Chrome, Firefox, Internet Explorer, Edge, Safari), navigate to the browser's plugin or add-on settings and verify if the Flash Player plugin is enabled or presentAffected if Any browser shows Flash Player plugin enabled and the version falls within the affected ranges listed above
You are affected if Adobe Flash Player or AIR is installed and the detected version number falls within any of the vulnerable version ranges: Flash Player 13.0 through 13.0.0.213 on Windows/macOS, Flash Player 11.0 through 11.2.202.358 on Linux, or AIR versions below 13.0.0.111.
Generated from the published advisory. Verify against your own configuration.
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 data11.2.202.35913.0.0.11113.0.0.214
Update Adobe Flash Player to version 13.0.0.214 or later (Windows/OS X) / 11.2.202.359 or later (Linux), and Adobe AIR SDK to 13.0.0.111 or later. Remove or disable Flash Player where possible given its end-of-life status.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2014-0517 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0517 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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