dbcve.org
Flash PlayerApplication · Adobe

CVE-2014-0545

HIGH · 10.0 CVSS v2.0 Published 2014-08-12
Fix available
A fix is available. Upgrade to after 14.0.0.137 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Adobe Flash Player before 13.0.0.241 and 14.x before 14.0.0.176 on Windows and OS X and before 11.2.202.400 on Linux, Adobe AIR before 14.0.0.178 on Windows and OS X and before 14.0.0.179 on Android, Adobe AIR SDK before 14.0.0.178, and Adobe AIR SDK & Compiler before 14.0.0.178 do not properly restrict discovery of memory addresses, which allows attackers to bypass the ASLR protection mechanism via unspecified vectors, a different vulnerability than CVE-2014-0540, CVE-2014-0542, CVE-2014-0543, and CVE-2014-0544.

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 confidence

This is a memory address disclosure vulnerability in Adobe Flash Player, AIR, and AIR SDK that fails to properly restrict discovery of memory addresses. Attackers can leverage this to bypass ASLR (Address Space Layout Randomization) protection by learning memory locations, making subsequent exploitation more reliable.

MitigationUpdate Adobe Flash Player to version 13.0.0.241/14.0.0.176 or later (11.2.202.400 on Linux), and Adobe AIR/SDK to 14.0.0.178 or later. Given Flash Player is end-of-life, organizations should consider removing it entirely if possible.

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
Flash PlayerApplication
Affected:<= 13.0.0.231= 13.0.0.182= 13.0.0.201= 13.0.0.206= 13.0.0.214= 13.0.0.223= 14.0.0.125= 14.0.0.145<= 11.2.202.394= 11.2.202.223= 11.2.202.228= 11.2.202.233
Adobe Air SdkApplication
Affected:<= 14.0.0.137= 13.0.0.83= 13.0.0.111= 14.0.0.110
Adobe AirApplication
Affected:<= 14.0.0.110= 13.0.0.83= 13.0.0.111<= 14.0.0.137= 14.0.0.110

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Adobe Flash Player version on Windows
    Open the Flash Player installation directory (typically C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash) and right-click the Flash*.ocx file to view Properties > Details. Alternatively, open a command prompt and run: dir /s C:\Windows\System32\Flash*.ocx
    Affected if The file version shown is 11.2.202.x where x is <= 394, or 13.0.0.x where x is <= 231, or 14.0.0.x where x is <= 145, or exactly matches 13.0.0.182, 13.0.0.201, 13.0.0.206, 13.0.0.214, 13.0.0.223, 14.0.0.125, or 14.0.0.145, or 11.2.202.223, 11.2.202.228, or 11.2.202.233
  2. Check Adobe Flash Player version in web browsers
    In Chrome, navigate to chrome://plugins and locate the Flash entry. In Firefox, navigate to about:addons and click Plugins. In Internet Explorer, go to Manage Add-ons. Record the version number displayed for the Shockwave Flash object.
    Affected if The reported Flash Player version is 11.2.202.x where x is <= 394, or 13.0.0.x where x is <= 231, or 14.0.0.x where x is <= 145, or exactly matches any of the specific vulnerable versions listed in the CVE.
  3. Check Adobe AIR runtime version on Windows
    Open Control Panel > Programs and Features, look for Adobe AIR in the list of installed programs, and note the version column. Alternatively, check the file version at C:\Program Files (x86)\Adobe\Adobe AIR\Versions\1.0\AdobeAIR.dll or similar path.
    Affected if The installed Adobe AIR version is <= 14.0.0.110, or exactly equals 13.0.0.83, 13.0.0.111, or 14.0.0.110, or is <= 14.0.0.137.
  4. Check Adobe AIR SDK version
    If the AIR SDK is installed, check the version file or readme in the SDK installation directory (commonly under C:\Program Files (x86)\Adobe\Adobe AIR SDK or C:\Program Files\Adobe\Adobe AIR SDK). Look for a version file or metadata that displays the SDK version number.
    Affected if The AIR SDK version is <= 14.0.0.137, or exactly equals 13.0.0.83, 13.0.0.111, or 14.0.0.110.

You are affected if any installed Adobe Flash Player, Adobe AIR, or Adobe AIR SDK version matches or falls within the vulnerable ranges listed in the CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 14.0.0.137
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.241/14.0.0.176 or later (11.2.202.400 on Linux), and Adobe AIR/SDK to 14.0.0.178 or later. Given Flash Player is end-of-life, organizations should consider removing it entirely if possible.

Recommended fix High confidence

Flash Player 13.x: 13.0.0.241+; Flash Player 14.x: 14.0.0.176+; Flash Player Linux: 11.2.202.400+; Adobe AIR Windows/OS X: 14.0.0.178+; Adobe AIR Android: 14.0.0.179+; Adobe AIR SDK: 14.0.0.178+

  1. 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the player context menu or visiting the version check page
  2. 2. Identify the currently installed Adobe AIR version via the AIR About screen or system control panel
  3. 3. For Flash Player: Download and install the fixed version 13.0.0.241 or later for 13.x branch, or 14.0.0.176 or later for 14.x branch from the official Adobe download page
  4. 4. For Adobe AIR: Download and install version 14.0.0.178 or later for Windows/OS X, or 14.0.0.179 or later for Android
  5. 5. For Adobe AIR SDK: Upgrade to version 14.0.0.178 or later
  6. 6. Restart any browsers and ensure Flash Player plugin is updated in all browser instances (Chrome, Firefox, IE, etc.)
  7. 7. Verify the installed version matches the fixed release by checking the Flash Player About page or AIR version information
Caveat Security-only updates with minimal risk; some older Flash content may have compatibility issues with newer player versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flash Player Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0545 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0545 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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