dbcve.org
Flash PlayerApplication · Adobe

CVE-2014-0544

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-0545.

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 an information disclosure vulnerability in Adobe Flash Player and AIR that allows attackers to discover memory addresses, enabling bypass of ASLR (Address Space Layout Randomization) protection. The flaw exists in unspecified vectors that fail to properly restrict memory address discovery.

MitigationUpdate Adobe Flash Player to version 13.0.0.241, 14.0.0.176, or 11.2.202.400 (Linux) or later; update Adobe AIR to 14.0.0.178 (Windows/OS X), 14.0.0.179 (Android), or later; and update AIR SDK/Compiler to 14.0.0.178 or later.

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 AirApplication
Affected:<= 14.0.0.110= 13.0.0.83= 13.0.0.111<= 14.0.0.137= 14.0.0.110
Adobe Air SdkApplication
Affected:<= 14.0.0.137= 13.0.0.83= 13.0.0.111= 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, check C:\Windows\System32\Macromed\Flash\FlashPlayerPlugin_*.exe version property, or in browsers go to https://helpx.adobe.com/flash-player.html. On Linux, check /usr/lib/flash-plugin/libflashplayer.so or run 'rpm -q flash-plugin' or dpkg -l. On Mac, check /Library/Application Support/Adobe/Flash Player/ or browser plugin location.
    Affected if Installed version is 13.0.0.231 or earlier, or any of these specific versions: 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, or 11.2.202.394/11.2.202.223/11.2.202.228/11.2.202.233
  2. Check Adobe AIR version on Windows
    Open Windows Control Panel > Programs and Features, look for Adobe AIR entry, or check C:\Program Files\Adobe\Adobe AIR\Versions\*\Adobe AIR Application Installer.exe version property.
    Affected if Installed version is 14.0.0.110 or earlier, or exactly version 13.0.0.83 or 13.0.0.111, or version 14.0.0.137 or earlier (Android-specific), or exactly 14.0.0.110
  3. Check Adobe AIR SDK version
    Check the SDK version by looking in the SDK installation directory for a version file, or run 'adl -version' from the SDK bin directory, or check the AIR SDK release notes file.
    Affected if Installed SDK version is 14.0.0.137 or earlier, or exactly version 13.0.0.83, 13.0.0.111, or 14.0.0.110
  4. Confirm if vulnerable Adobe components are in use
    Check running processes for flash*.exe, plugin-container processes, or Adobe AIR application processes. On Windows servers or workstations with browser access, enumerate installed browser plugins for Flash Player.
    Affected if Any affected version of Flash Player, AIR runtime, or AIR SDK is installed and actively in use on the system

You are affected if Adobe Flash Player, Adobe AIR runtime, or Adobe AIR SDK matching any of the specific versions listed in the affected versions range is installed and running on your system.

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 11.2.202.400 (Linux) or later; update Adobe AIR to 14.0.0.178 (Windows/OS X), 14.0.0.179 (Android), or later; and update AIR SDK/Compiler to 14.0.0.178 or later.

Recommended fix High confidence

Flash Player: 14.0.0.176 (Win/OS X), 13.0.0.241, or 11.2.202.400 (Linux); Adobe AIR: 14.0.0.178 (Win/OS X) or 14.0.0.179 (Android); Adobe AIR SDK: 14.0.0.178

  1. 1. Identify the installed Adobe product (Flash Player, Adobe AIR, or Adobe AIR SDK) and its current version
  2. 2. For Flash Player on Windows/OS X: Upgrade to version 14.0.0.176 or later, or 13.0.0.241 or later
  3. 3. For Flash Player on Linux: Upgrade to version 11.2.202.400 or later
  4. 4. For Adobe AIR on Windows/OS X: Upgrade to version 14.0.0.178 or later
  5. 5. For Adobe AIR on Android: Upgrade to version 14.0.0.179 or later
  6. 6. For Adobe AIR SDK: Upgrade to version 14.0.0.178 or later
  7. 7. Download the fixed version from the official Adobe Security Bulletin APSB14-18: http://helpx.adobe.com/security/products/flash-player/apsb14-18.html
  8. 8. Uninstall the old version and install the new fixed version
Caveat Flash Player 14.x requires browser plugin compatibility; some older systems may not support newer versions

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0544 — 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-0544 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