dbcve.org
Adobe AirApplication · Adobe

CVE-2014-0550

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-0551, CVE-2014-0552, and CVE-2014-0555.

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 arbitrary code execution or denial of service. Affects specific versions across Windows, OS X, Linux, and Android platforms.

MitigationUpgrade to Flash Player 13.0.0.244 (Windows/OS X), 11.2.202.406 (Linux), or 15.0.0.152 (14.x/15.x); upgrade 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. Check Flash Player version on Windows or macOS
    Navigate to Control Panel (Windows) or System Preferences (macOS), select Flash Player, and view the version in the Storage tab. Alternatively, visit Adobe's version check page at about:flash in a browser.
    Affected if The displayed version matches any of: 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, or is less than or equal to 11.2.202.400 (for 11.x branch).
  2. Check Flash Player version on Linux
    Locate the file libflashplayer.so in /usr/lib/flash-plugin/, /usr/lib64/flash-plugin/, or /opt/flash-plugin/. Right-click the file, select Properties, and view the version on the Version tab.
    Affected if The version matches any of the specific versions listed for Windows/macOS above, or is less than or equal to 11.2.202.400.
  3. Check Adobe AIR version on Windows or macOS
    On Windows, open Add or Remove Programs and locate Adobe AIR. On macOS, open Finder, navigate to /Applications/Utilities, and run Adobe AIR Application Installer to see the installed version, or check the version from the AIR app properties.
    Affected if The installed version is 13.0.0.83, 13.0.0.111, 14.0.0.110, 14.0.0.137, or less than or equal to 14.0.0.178 (or 14.0.0.179 depending on exact patch level).
  4. Check Adobe AIR SDK version
    Locate the AIR SDK installation directory. Open the README or version file within the SDK folder, or run 'adl -version' if the SDK tools are in the PATH.
    Affected if The SDK version is 13.0.0.83, 13.0.0.111, 14.0.0.110, 14.0.0.137, or less than or equal to 14.0.0.178.
  5. Check Adobe AIR version on Android
    Open Settings on the Android device, go to Apps or Application Manager, find Adobe AIR in the list, and view the version information.
    Affected if The version matches any of the affected AIR versions listed for desktop platforms.

Your environment is affected if any installed Flash Player, AIR, or AIR SDK version matches or falls within the specific version numbers and ranges listed in the affected products, regardless of platform.

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

Upgrade to Flash Player 13.0.0.244 (Windows/OS X), 11.2.202.406 (Linux), or 15.0.0.152 (14.x/15.x); upgrade AIR to 15.0.0.249 (Windows/OS X) or 15.0.0.252 (Android).

Recommended fix High confidence

Flash Player 15.0.0.152+ (Windows/OS X), 13.0.0.244+ (13.x branch), 11.2.202.406+ (Linux); Adobe AIR 15.0.0.249+ (Windows/OS X), 15.0.0.252+ (Android); Adobe AIR SDK 15.0.0.249+

  1. Identify the currently installed Adobe Flash Player or AIR version by navigating to About Flash Player or checking the system's installed programs
  2. Download the appropriate fixed version from the official Adobe security bulletin: http://helpx.adobe.com/security/products/flash-player/apsb14-21.html
  3. For Windows/OS X users: Upgrade to Flash Player 15.0.0.152 or later (or 13.0.0.244 for the 13.x branch)
  4. For Linux users: Upgrade to Flash Player 11.2.202.406 or later
  5. For Adobe AIR (Windows/OS X): Upgrade to version 15.0.0.249 or later
  6. For Adobe AIR (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. Restart any browsers or applications using Flash Player after installation
Caveat Flash Player 15.x introduced PPAPI architecture changes on Windows; ensure browser compatibility before upgrading

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

Fix this in Adobe Air Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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