CVE-2014-0585
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.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 by leveraging an unspecified "type confusion," a different vulnerability than CVE-2014-0577, CVE-2014-0584, CVE-2014-0586, and CVE-2014-0590.
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 confidenceType confusion vulnerability in Adobe Flash Player and AIR allows remote attackers to execute arbitrary code via unspecified vectors. The vulnerability stems from improper type handling that can lead to memory corruption and code execution.
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.252>= 14.0, <= 14.0.0.179>= 15.0, < 15.0.0.223>= 11.0, < 11.2.202.418<= 15.0.0.356<= 15.0.0.356< 15.0.0.356CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Adobe Flash Player version on WindowsOpen Control Panel > Programs and Features, find Adobe Flash Player in the list, and note the version columnAffected if The version is 13.0.0.0 through 13.0.0.251, 14.0.0.0 through 14.0.0.179, 15.0.0.0 through 15.0.0.222, or 11.0.0.0 through 11.2.202.417
-
Check Adobe Flash Player version in browsersVisit the Adobe version check page at get.adobe.com/flashplayer/about or look at the Flash NPAPI/PPAPI DLL file properties in browser plugin directoriesAffected if The reported version matches any of the affected ranges listed above
-
Check Adobe Flash Player on LinuxOpen terminal and run rpm -q flash-player or check the version in the Firefox Add-ons plugin managerAffected if The version is 11.2.202.417 or earlier
-
Check Adobe AIR versionOpen Control Panel > Programs and Features, locate Adobe AIR, and note the version; or run 'airpackager -version' from the SDK if installedAffected if The version is 15.0.0.356 or earlier, or the SDK version is below 15.0.0.356
-
Identify if Flash Player plugin is activeIn web browsers, navigate to about:addons (Firefox) or chrome://plugins (Chrome) and verify if Flash is enabledAffected if Flash is listed as enabled and the version falls within the affected ranges
You are affected if Adobe Flash Player version is 13.0.0.0-13.0.0.251, 14.0.0.0-14.0.0.179, 15.0.0.0-15.0.0.222, or 11.0.0.0-11.2.202.417, or Adobe AIR version is 15.0.0.356 or earlier.
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.
dbcve · scoped11.2.202.41813.0.0.25215.0.0.223
Update Adobe Flash Player to version 13.0.0.252 or later (14.x/15.x to 15.0.0.223), Linux to 11.2.202.418 or later, and Adobe AIR to 15.0.0.356 or later. Consider Flash removal if unnecessary given end-of-life status.
Flash Player 13.0.0.252+/14.0.0.180+/15.0.0.223+/11.2.202.418+; AIR 15.0.0.356+; AIR SDK 15.0.0.356+
- Identify the installed version of Adobe Flash Player or AIR on the system
- Navigate to Adobe's official security bulletin at helpx.adobe.com/security/products/flash-player/apsb14-24.html
- Download the appropriate fixed version: Flash Player 13.0.0.252 or later, 14.0.0.180 or later, 15.0.0.223 or later, or 11.2.202.418 or later for Linux; AIR 15.0.0.356 or later; AIR SDK 15.0.0.356 or later
- Install the updated Flash Player or AIR version
- Restart any browsers or applications using Flash Player or AIR
- Verify the installed version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0585 — 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-0585 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