CVE-2014-0581
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 or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2014-0576, CVE-2014-8440, and CVE-2014-8441.
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 allowing arbitrary code execution via unspecified vectors. Affects Flash Player versions before 13.0.0.252/15.0.0.223 on Windows/OS X, before 11.2.202.418 on Linux, and Adobe AIR/SDK before 15.0.0.356.
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 Flash Player version in Windows browsersOpen a browser and navigate to 'about:flash' (Chrome) or 'about:plugin' (Firefox), or go to https://helpx.adobe.com/flash-player.html and check the version displayed. Alternatively, check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion for the 'Version' value.Affected if The reported version is less than 13.0.0.252 (for 13.x branch), less than 15.0.0.223 (for 14.x/15.x branch), or less than 11.2.202.418 (Linux).
-
Check Flash Player version in macOS browsersOpen System Preferences and click on Flash Player, or navigate to /Library/Application Support/Adobe/Flash Player/ and check the version file. In Safari, enable the Develop menu and check the installed plugins.Affected if The reported version is less than 13.0.0.252 (for 13.x branch) or less than 15.0.0.223 (for 14.x/15.x branch).
-
Check Flash Player version on LinuxRun 'dpkg -l | grep flash' or 'rpm -qa | grep flash' to list installed flash-plugin packages. Also check /usr/lib/flash-plugin/ for version files or run 'flash-player-properties' to open the settings dialog showing the version.Affected if The reported version is less than 11.2.202.418.
-
Check Adobe AIR version on WindowsOpen the Windows Control Panel and look for Adobe AIR in the installed programs list, or check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR\Version for the 'Version' value.Affected if The reported version is 15.0.0.356 or earlier.
-
Check Adobe AIR SDK versionLocate the AIR SDK installation directory and check the version file (typically named 'VERSION' or 'readme.txt'), or run 'adt -version' if the AIR Developer Tool is in your PATH.Affected if The AIR SDK version shown is 15.0.0.356 or earlier.
Your environment is affected if Adobe Flash Player is installed at any version below 13.0.0.252, 14.0.0.179, 15.0.0.223, or 11.2.202.418 (Linux), or if Adobe AIR/SDK is at version 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 (15.0.0.223 for 14.x/15.x branches) and Adobe AIR/SDK to 15.0.0.356 or later. Consider removing Flash Player if unnecessary given its end-of-life status.
Flash Player: 13.0.0.252, 15.0.0.223, or 11.2.202.418 (depending on branch); Adobe AIR/AIR SDK: 15.0.0.356
- Navigate to the Adobe Flash Player download center or use the Adobe Update Manager
- Download Flash Player version 13.0.0.252 or later (for 13.x branch), 15.0.0.223 or later (for 14.x/15.x), or 11.2.202.418 (for Linux 11.x)
- For Adobe AIR installations, download and install version 15.0.0.356 or later from the Adobe AIR download page
- Restart all browsers and applications that use Flash Player or AIR
- Verify the installed version matches the fixed release using the Adobe version check page at get.adobe.com/flashplayer
Generated from the published advisory — verify against the referenced sources before acting.
- 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-0581 — 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-0581 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