CVE-2014-0564
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.250 and 14.x and 15.x before 15.0.0.189 on Windows and OS X and before 11.2.202.411 on Linux, Adobe AIR before 15.0.0.293, Adobe AIR SDK before 15.0.0.302, and Adobe AIR SDK & Compiler before 15.0.0.302 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2014-0558.
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 confidenceMemory corruption vulnerability in Adobe Flash Player and AIR allows attackers to execute arbitrary code or cause denial of service via unspecified vectors. The flaw affects multiple versions across Windows, OS X, and Linux platforms.
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<= 11.2.202.406<= 13.0.0.244<= 15.0.0.152<= 15.0.0.167<= 15.0.0.167<= 15.0.0.249<= 15.0.0.249<= 15.0.0.252= 11.4= 12.3= 13.1= 11CVSS 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 Flash Player version on WindowsOpen Windows Registry Editor (regedit) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion, or open a command prompt and run: 'reg query "HKLM\SOFTWARE\Macromedia\FlashPlayer" /v CurrentVersion'Affected if The version displayed is less than or equal to 11.2.202.406, 13.0.0.244, 15.0.0.152, or 15.0.0.167
-
Check Flash Player version on LinuxOpen a terminal and run: 'rpm -q flash-plugin' for RPM-based systems, or check /usr/lib/flash-plugin/libflashplayer.so version info, or look in /usr/share/flash-player-properties/Affected if The installed version is 11.2.202.406 or earlier, or 13.0.0.244 or earlier, or 15.0.0.152 or earlier, or 15.0.0.167 or earlier
-
Check Flash Player version on macOSOpen Finder, navigate to /Library/Application Support/Adobe/Flash Player/ and check the version, or use terminal command: 'ls /Library/Application Support/Adobe/Flash Player/'Affected if The version folder or file indicates a version <= 11.2.202.406, <= 13.0.0.244, <= 15.0.0.152, or <= 15.0.0.167
-
Check Adobe AIR versionOn Windows, check Add/Remove Programs for Adobe AIR version, or check C:\Program Files (x86)\Adobe\Adobe AIR\Versions\1.0\Adobe AIR Application Installer.exe properties; on Linux check via 'rpm -q adobe-air' or examine /opt/adobe-air/versions.xml; on macOS check /Applications/Adobe AIR Installer.appAffected if The installed version is 15.0.0.249 or earlier (Desktop Runtime) or 15.0.0.249/15.0.0.252 or earlier (SDK)
-
Identify if running affected openSUSE or SUSE Linux EnterpriseCheck OS version via 'cat /etc/SuSE-release' or 'cat /etc/os-release' and confirm it is openSUSE 11.4, 12.3, 13.1, or SUSE Linux Enterprise Desktop 11Affected if The system is running openSUSE 11.4, 12.3, 13.1, or SUSE Linux Enterprise Desktop 11 with Adobe Flash Player installed
If the installed Adobe Flash Player version is 11.2.202.406 or earlier on Linux, 13.0.0.244 or earlier on Windows/OS X, 15.0.0.152/15.0.0.167 or earlier in any branch, or Adobe AIR is 15.0.0.249 or earlier, the system is vulnerable to CVE-2014-0564.
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 · scopedUpdate Adobe Flash Player to version 13.0.0.250+ (Windows/OS X), 11.2.202.411+ (Linux), or 15.0.0.189+ for v14/15 branches; update Adobe AIR and SDK to 15.0.0.293/302 or later.
Flash Player: upgrade to 13.0.0.250+ (13.x), 15.0.0.189+ (14.x/15.x), or 11.2.202.411+ (Linux); Adobe AIR: upgrade to 15.0.0.293+; Adobe AIR SDK: upgrade to 15.0.0.302+
- Identify the currently installed Adobe Flash Player or Adobe AIR version on the system
- For Flash Player: Navigate to Adobe's official download page or use the system's software update mechanism
- For Adobe AIR: Download the latest Adobe AIR runtime or SDK from Adobe's official website
- Download and install the appropriate fixed version based on your operating system and product type
- For Linux systems using system package managers, apply the updated packages from your distribution's security repository (e.g., openSUSE update repositories, Red Hat channels)
- Verify the installed version matches the fixed release (Flash Player 13.0.0.250 or higher for 13.x, 15.0.0.189 or higher for 14.x/15.x, 11.2.202.411 for Linux; Adobe AIR 15.0.0.293 or higher; AIR SDK 15.0.0.302 or higher)
- Restart any affected browsers or applications that use Flash Player
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-0564 — 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-0564 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