dbcve.org
Adobe AirApplication · Adobe

CVE-2014-0555

HIGH · 10.0 CVSS v2.0 Published 2014-09-10
Fix available
A fix is available. Upgrade to after 14.0.0.179 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.244 and 14.x and 15.x before 15.0.0.152 on Windows and OS X and before 11.2.202.406 on Linux, Adobe AIR before 15.0.0.249 on Windows and OS X and before 15.0.0.252 on Android, Adobe AIR SDK before 15.0.0.249, and Adobe AIR SDK & Compiler before 15.0.0.249 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2014-0547, CVE-2014-0549, CVE-2014-0550, CVE-2014-0551, and CVE-2014-0552.

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

Memory corruption vulnerability in Adobe Flash Player and AIR allowing remote code execution or denial of service via unspecified vectors. The vulnerability affects multiple platforms (Windows, OS X, Linux, Android) and multiple product versions, with a CVSS score of 10 indicating critical severity with complete confidentiality, integrity, and availability impact.

MitigationApply vendor patches by updating Adobe Flash Player to versions 13.0.0.244, 14.x/15.x to 15.0.0.152 (Windows/OS X) or 11.2.202.406 (Linux), and Adobe AIR to 15.0.0.249 (Windows/OS X) or 15.0.0.252 (Android).

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
Adobe AirApplication
Affected:<= 14.0.0.178= 13.0.0.83= 13.0.0.111= 14.0.0.110= 14.0.0.137<= 14.0.0.179
Flash PlayerApplication
Affected:<= 11.2.202.400= 11.2.202.223= 11.2.202.228= 11.2.202.233= 11.2.202.235= 11.2.202.236= 11.2.202.238= 11.2.202.243= 11.2.202.251= 11.2.202.258= 11.2.202.261= 11.2.202.262
Adobe Air SdkApplication
Affected:<= 14.0.0.178= 13.0.0.83= 13.0.0.111= 14.0.0.110= 14.0.0.137

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. Identify installed Flash Player version in Windows
    Open regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion, or check the file properties of NPSWF32.dll in the System32 or SysWOW64 folder
    Affected if The version listed is 11.2.202.400 or lower, or exactly matches any of these: 11.2.202.223, 11.2.202.228, 11.2.202.233, 11.2.202.235, 11.2.202.236, 11.2.202.238, 11.2.202.243, 11.2.202.251, 11.2.202.258, 11.2.202.261, or 11.2.202.262
  2. Identify installed Flash Player version in Linux
    Run rpm -q npp or dpkg -l | grep flash, or check the version via the Firefox about:plugins page
    Affected if The version listed is 11.2.202.400 or lower, or exactly matches any of the specific versions listed for Windows Flash Player
  3. Identify installed Adobe AIR version on Windows
    Open regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\AIR\VersionInfo, or check the file properties of the AIR.dll in the installation folder (typically C:\Program Files\Adobe\Adobe AIR)
    Affected if The version is 14.0.0.178 or lower, or exactly matches 13.0.0.83, 13.0.0.111, 14.0.0.110, or 14.0.0.137
  4. Identify installed Adobe AIR version on OS X
    Check the Get Info window of Adobe AIR.app in /Applications, or run: defaults read /Applications/Adobe\ AIR.app/Contents/Info CFBundleVersion
    Affected if The version is 14.0.0.178 or lower, or exactly matches 13.0.0.83, 13.0.0.111, 14.0.0.110, or 14.0.0.137
  5. Check for Adobe AIR SDK installation
    Locate the AIR SDK by finding the file AIRSDK.version or airmxmlc.exe, then check its version properties or run: adt -version if installed
    Affected if The AIR SDK version is 14.0.0.178 or lower, or exactly matches 13.0.0.83, 13.0.0.111, 14.0.0.110, or 14.0.0.137

You are affected if any installed Adobe Flash Player version is 11.2.202.400 or lower, or any installed Adobe AIR version is 14.0.0.178 or lower (including the specific versions listed), as these versions contain the memory corruption flaw.

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.179
Vendor patch helpx.adobe.com →
Interim mitigation

Apply vendor patches by updating Adobe Flash Player to versions 13.0.0.244, 14.x/15.x to 15.0.0.152 (Windows/OS X) or 11.2.202.406 (Linux), and Adobe AIR to 15.0.0.249 (Windows/OS X) or 15.0.0.252 (Android).

Recommended fix High confidence

Adobe Flash Player 13.0.0.244+/15.0.0.152+, Adobe AIR 15.0.0.249+, Adobe AIR SDK 15.0.0.249+ (depending on platform and product)

  1. Identify the installed Adobe Flash Player, Adobe AIR, or Adobe AIR SDK version
  2. For Flash Player 13.x on Windows/OS X: upgrade to version 13.0.0.244 or later
  3. For Flash Player 14.x/15.x on Windows/OS X: upgrade to version 15.0.0.152 or later
  4. For Flash Player on Linux: upgrade to version 11.2.202.406 or later
  5. For Adobe AIR on Windows/OS X: upgrade to version 15.0.0.249 or later
  6. For Adobe AIR on Android: upgrade to version 15.0.0.252 or later
  7. For Adobe AIR SDK: upgrade to version 15.0.0.249 or later
  8. Download the appropriate update from the official Adobe security bulletin at http://helpx.adobe.com/security/products/flash-player/apsb14-21.html
Caveat Adobe Flash Player reached end-of-life in December 2020; consider migrating away from Flash-based applications if possible

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

Fix this in Adobe Air Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

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