dbcve.org
Adobe AirApplication · Adobe

CVE-2014-0554

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 bypass intended access restrictions 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 · moderate confidence

Adobe Flash Player and Adobe AIR contain an access restriction bypass vulnerability that allows remote attackers to circumvent security controls. The vulnerability affects multiple product lines across Windows, OS X, Linux, and Android platforms, with the specific attack vectors not disclosed in the advisory.

MitigationApply the vendor-provided patches by updating to Adobe Flash Player 13.0.0.244, 15.0.0.152, or 11.2.202.406 (depending on platform), or Adobe AIR 15.0.0.249/252 or later. Consider disabling Flash Player in browsers until patches can be applied, given the critical severity.

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.179= 13.0.0.83= 13.0.0.111= 14.0.0.110= 14.0.0.137<= 14.0.0.178
Flash PlayerApplication
Affected:<= 13.0.0.241= 13.0.0.182= 13.0.0.201= 13.0.0.206= 13.0.0.214= 13.0.0.223= 13.0.0.231= 14.0.0.125= 14.0.0.145= 14.0.0.176= 14.0.0.179= 15.0.0.144
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 Adobe products
    Check for Adobe Flash Player in browsers (about:plugins in Firefox, chrome://plugins in Chrome) or check for Adobe AIR applications. On Windows, search for NPSWF32.dll (Flash) or AIR application files.
    Affected if Either Adobe Flash Player or Adobe AIR is present on the system
  2. Check Flash Player version in browsers
    In Firefox, go to about:plugins and look for Shockwave Flash. In Chrome, go to chrome://plugins. Note the Version field. On Windows, also check the file properties of NPSWF32.dll in the browser plugins folder.
    Affected if The displayed version matches any of: 13.0.0.182, 201, 206, 214, 223, 231, 241, 14.0.0.125, 145, 176, 179, 15.0.0.144, or any version <= 13.0.0.241, or any version <= 14.0.0.178 (for 14.x branch before 14.0.0.179)
  3. Check Adobe AIR version
    Open the AIR application and check its version, or check the AIR runtime version via registry (HKLM\SOFTWARE\Adobe\AIR on Windows) or application manifest files.
    Affected if The AIR version is 13.0.0.83, 13.0.0.111, 14.0.0.110, 14.0.0.137, or any version <= 14.0.0.178, or exactly 14.0.0.179
  4. Check Adobe AIR SDK version
    If you are a developer using AIR SDK, check the version file in the SDK installation directory (typically version.txt or the AIR SDK descriptor).
    Affected if The AIR SDK version is 13.0.0.83, 13.0.0.111, 14.0.0.110, 14.0.0.137, or any version <= 14.0.0.178
  5. Verify platform applicability
    Confirm the operating system: this CVE affects Windows, OS X, Linux, and Android. Check system OS version.
    Affected if The system runs any of these platforms and the installed product version matches the affected ranges

The environment is affected if Adobe Flash Player version is 13.0.0.182/201/206/214/223/231/241, 14.0.0.125/145/176/179, 15.0.0.144, or <=13.0.0.241, or <=14.0.0.178; or Adobe AIR version is 13.0.0.83/111, 14.0.0.110/137/179, or <=14.0.0.178/179; or Adobe AIR SDK matches those same AIR versions.

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 the vendor-provided patches by updating to Adobe Flash Player 13.0.0.244, 15.0.0.152, or 11.2.202.406 (depending on platform), or Adobe AIR 15.0.0.249/252 or later. Consider disabling Flash Player in browsers until patches can be applied, given the critical severity.

Recommended fix High confidence

Adobe AIR 15.0.0.249 (or later); Flash Player 13.0.0.244 (or later) / 15.0.0.152 (or later for 14.x/15.x); Adobe AIR SDK 15.0.0.249 (or later)

  1. 1. Identify the exact Adobe product installed (Flash Player, AIR, or AIR SDK) and its current version
  2. 2. For Flash Player: upgrade to version 13.0.0.244 or later, or version 15.0.0.152 or later for 14.x/15.x
  3. 3. For Adobe AIR: upgrade to version 15.0.0.249 or later for Windows/OS X, or version 15.0.0.252 or later for Android
  4. 4. For Adobe AIR SDK: upgrade to version 15.0.0.249 or later
  5. 5. Verify the upgrade was successful by checking the product version
Caveat Upgrading to major version 15 may introduce compatibility changes with older content or applications; test critical workflows before deployment

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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