dbcve.org
Adobe AirApplication · Adobe

CVE-2014-0552

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

Adobe Flash Player and AIR contain a memory corruption vulnerability allowing arbitrary code execution or denial of service. The vulnerability affects specific versions across Windows, OS X, Linux, and Android platforms before the patched releases.

MitigationUpdate Adobe Flash Player to version 13.0.0.244 or later (14.x/15.x to 15.0.0.152 or later, Linux to 11.2.202.406 or later), and AIR to 15.0.0.249 or later (Android 15.0.0.252 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
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 on Windows
    Open Control Panel > Programs and Features, look for Adobe Flash Player XX.X.X XXX in the list, or visit https://helpx.adobe.com/flash-player.html on the system and check the version displayed
    Affected if The listed version matches any of: <= 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, or any 13.x version below 13.0.0.244, or any 14.x/15.x version below 15.0.0.152, or Linux 11.x
  2. Identify installed Flash Player version on Mac
    Open Safari, go to Adobe's version check page at adobe.com/software/flash/about, or use terminal command: defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersion
    Affected if The displayed version matches any of the affected versions listed above for Flash Player (same ranges as Windows check)
  3. Identify installed Adobe AIR version on Windows
    Open Control Panel > Programs and Features, look for Adobe AIR in the list, or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR for DisplayVersion
    Affected if The version is <= 14.0.0.178, equals 13.0.0.83, 13.0.0.111, 14.0.0.110, or 14.0.0.137, or any version <= 14.0.0.179 (note: versions 15.0.0.249 and later are fixed)
  4. Identify installed Adobe AIR version on Mac
    Open System Information > Applications, or check /Library/Application Support/Adobe AIR/Versions/<version>/Info.plist for CFBundleVersion
    Affected if Same version conditions as Windows Adobe AIR check apply
  5. Check for Adobe AIR SDK installed
    Look for AIR SDK in the installation directory (commonly C:\Program Files\Adobe\Adobe AIR SDK or /Applications/Adobe AIR SDK), open the AIR SDK Readme.txt or check the version file included in the SDK folder
    Affected if The AIR SDK version is <= 14.0.0.178, equals 13.0.0.83, 13.0.0.111, 14.0.0.110, or 14.0.0.137

A system is affected if Adobe Flash Player, Adobe AIR, or Adobe AIR SDK version matches any of the specific versions or version ranges listed as vulnerable for this 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.179
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.244 or later (14.x/15.x to 15.0.0.152 or later, Linux to 11.2.202.406 or later), and AIR to 15.0.0.249 or later (Android 15.0.0.252 or later).

Recommended fix High confidence

Adobe Flash Player 13.0.0.244 (13.x), 15.0.0.152 (14.x/15.x Windows/OS X), 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. 1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click menu or visiting the version check page.
  2. 2. Identify the installed Adobe AIR version via the application's 'About' dialog or system registry.
  3. 3. Download the appropriate fixed version from the Adobe Security Bulletin APSB14-21: http://helpx.adobe.com/security/products/flash-player/apsb14-21.html
  4. 4. For Flash Player: Upgrade to version 13.0.0.244 (if using 13.x), 15.0.0.152 (if using 14.x/15.x on Windows/OS X), or 11.2.202.406 (if using Linux).
  5. 5. For Adobe AIR: Upgrade to version 15.0.0.249 (Windows/OS X) or 15.0.0.252 (Android).
  6. 6. For Adobe AIR SDK: Upgrade to version 15.0.0.249.
  7. 7. Restart any running browser or AIR applications after installation.
  8. 8. Verify the installed version matches the fixed release by re-checking the version information.
Caveat Ensure compatibility with web content and AIR applications as minor version upgrades may have behavioral changes; AIR 15.x requires OS X 10.7+ or Windows 7+

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
  • 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-0552 — 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-0552 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