CVE-2014-0588
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 · uneditedUse-after-free vulnerability in 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 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2014-0573 and CVE-2014-8438.
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 confidenceUse-after-free vulnerability in Adobe Flash Player and Adobe AIR allowing remote attackers to execute arbitrary code via unspecified vectors. Affected versions span multiple platforms (Windows, OS X, Linux) and product lines (Flash Player, AIR, AIR SDK).
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 if Adobe Flash Player is installedOn Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer or check for npflash.dll in browser plugin directories. On Mac, check /Library/Internet Plug-Ins/ for Flash Player.plugin. On Linux, check /usr/lib/flash-plugin/ or /usr/lib64/flash-plugin/Affected if Flash Player is found on the system
-
Determine the installed Flash Player versionOn Windows, run 'reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer" /v Version' or right-click the npflash.dll file and select Properties > Details. On Mac, right-click Flash Player.plugin and select Get Info to view the version. On Linux, run 'rpm -q flash-plugin' or check the version file in the plugin directoryAffected if A version number is returned that can be compared to the affected ranges
-
Compare the Flash Player version against affected rangesCheck if the installed version falls within any of these vulnerable ranges: 11.0 to 11.2.202.417, 13.0 to 13.0.0.251, 14.0 to 14.0.0.179, or 15.0 to 15.0.0.222. Versions at or above the upper bound of each range are not affectedAffected if The installed version is less than 11.2.202.418, or between 13.0.0.0 and 13.0.0.251, or between 14.0.0.0 and 14.0.0.179, or between 15.0.0.0 and 15.0.0.222
-
Check if Adobe AIR is installedOn Windows, look in C:\Program Files\Adobe\Adobe AIR\ or check Add/Remove Programs. On Mac, check /Applications/Adobe AIR Installer.app or the Applications folder. On Linux, check /opt/adobe-air-sdk/ or use package managerAffected if Adobe AIR or Adobe AIR SDK is found on the system
-
Determine the installed Adobe AIR versionOn Windows, right-click the Adobe AIR application file and select Properties > Details. On Mac, right-click Adobe AIR Installer.app and select Get Info. For SDK, check the version in the SDK manifest or about fileAffected if A version number is returned that can be compared to the affected ranges
-
Compare the Adobe AIR version against affected rangesCheck if the installed AIR version or AIR SDK version is less than 15.0.0.356. Versions from 15.0.0.356 and above are patchedAffected if The installed Adobe AIR, AIR SDK, or AIR SDK & Compiler version is below 15.0.0.356
The system is affected if any installed Adobe Flash Player version is within 11.0-11.2.202.417, 13.0-13.0.0.251, 14.0-14.0.179, or 15.0-15.0.0.222, OR if any Adobe AIR/SDK version is below 15.0.0.356
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
Upgrade Adobe Flash Player to 13.0.0.252/15.0.0.223 or later, and Adobe AIR/SDK to 15.0.0.356 or later. Alternatively, remove or disable Flash Player if unnecessary.
Flash Player 13.0.0.252 (or 15.0.0.223 for 14.x/15.x tracks); Flash Player 11.2.202.418 for Linux; Adobe AIR 15.0.0.356
- 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click menu or visiting the Adobe version check page.
- 2. Identify the currently installed Adobe AIR version from the Windows Control Panel or Mac Applications folder.
- 3. Download the appropriate fixed version from the Adobe Security Bulletin APSB14-24: http://helpx.adobe.com/security/products/flash-player/apsb14-24.html
- 4. For Flash Player 11.x on Linux: Upgrade to version 11.2.202.418
- 5. For Flash Player 13.x: Upgrade to version 13.0.0.252
- 6. For Flash Player 14.x/15.x: Upgrade to version 15.0.0.223
- 7. For Adobe AIR and AIR SDK: Upgrade to version 15.0.0.356
- 8. Close all browser instances and any applications using Flash/AIR before installing the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0588 — 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-0588 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