CVE-2014-0536
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.223 and 14.x before 14.0.0.125 on Windows and OS X and before 11.2.202.378 on Linux, Adobe AIR before 14.0.0.110, Adobe AIR SDK before 14.0.0.110, and Adobe AIR SDK & Compiler before 14.0.0.110 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.
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 confidenceAdobe Flash Player and Adobe AIR contain a memory corruption vulnerability that allows remote attackers to execute arbitrary code or cause a denial of service via unspecified vectors. The vulnerability stems from improper memory handling that can be exploited to achieve 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<= 11.2.202.359<= 13.0.0.214= 13.0.0.182= 13.0.0.201= 13.0.0.206<= 13.0.0.111= 13.0.0.83<= 13.0.0.111= 13.0.0.83CVSS 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, or navigate to C:\Windows\System32\Macromed\Flash and check the file properties of the installed Flash DLL. Alternatively, visit Adobe's version check page at get.adobe.com/flashplayer in the browser.Affected if The installed version is 11.2.202.359 or earlier, 13.0.0.214 or earlier, or exactly 13.0.0.182, 13.0.0.201, or 13.0.0.206
-
Check Adobe Flash Player version on MacNavigate to /Library/Application Support/Adobe/Flash Player/ and check the version folder, or open Safari and visit Adobe's version check page.Affected if The installed version matches the Windows criteria above.
-
Check Adobe Flash Player version on LinuxCheck /usr/lib/flash-plugin/ for the version, or run rpm -q flash-plugin or dpkg -l | grep flash to query installed packages.Affected if The installed version is 11.2.202.359 or earlier.
-
Check Adobe AIR versionOpen Adobe AIR from the Start Menu (Windows) or Applications folder (Mac), or on Windows navigate to C:\Program Files\Adobe\Adobe AIR and check the file properties. On Mac, check /Applications/Adobe AIR.app.Affected if The installed version is 13.0.0.111 or earlier, or exactly 13.0.0.83
-
Check Adobe AIR SDK versionOpen the AIR SDK release notes or check the version file within the installed AIR SDK directory. If using a development tool, check the SDK version configured in the project settings.Affected if The installed SDK version is 13.0.0.111 or earlier, or exactly 13.0.0.83
A system is affected if Adobe Flash Player is version 11.2.x up to 202.359, 13.0.x up to 214, or exactly 13.0.0.182/201/206; or if Adobe AIR/SDK is version 13.0.0.111 or earlier, or exactly 13.0.0.83.
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.223 or later (14.x to 14.0.0.125, Linux to 11.2.202.378), and Adobe AIR/SDK to 14.0.0.110 or later. Given the CVSS 10 severity and arbitrary code execution capability, prioritize patching all affected systems immediately.
Flash Player 13.0.0.223+/14.0.0.125+/11.2.202.378+ (Linux); Adobe AIR 14.0.0.110+; Adobe AIR SDK 14.0.0.110+
- 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click menu or visiting 'about:flash' in the browser
- 2. Identify the currently installed Adobe AIR version from the system's installed programs list
- 3. For Flash Player 13.x users: Download and install Flash Player 13.0.0.223 or later from the Adobe website
- 4. For Flash Player 14.x users: Download and install Flash Player 14.0.0.125 or later from the Adobe website
- 5. For Flash Player 11.x on Linux: Download and install Flash Player 11.2.202.378 or later from the Adobe website
- 6. For Adobe AIR users: Download and install Adobe AIR 14.0.0.110 or later
- 7. For Adobe AIR SDK users: Download and install Adobe AIR SDK 14.0.0.110 or later from the Adobe AIR SDK download page
- 8. Restart all browsers after updating Flash Player
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0536 — 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-0536 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