dbcve.org
Flash PlayerApplication · Adobe

CVE-2014-0547

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-0549, CVE-2014-0550, 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 remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. Affects multiple platforms including Windows, OS X, Linux, and Android across specific version ranges.

MitigationUpgrade to Adobe Flash Player 13.0.0.244, 15.0.0.152 (14.x/15.x), or 11.2.202.406 (Linux); upgrade Adobe AIR to 15.0.0.249 (Windows/OS X) or 15.0.0.252 (Android); consider disabling Flash Player as an interim measure.

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.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 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
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. Identify installed Adobe Flash Player version
    On Windows, open Control Panel > Programs and Features and look for 'Adobe Flash Player XX' entry, or check the version in your browser by navigating to about:plugins (Firefox) or chrome://plugins (Chrome). On macOS, check /Library/Internet\ Plug-Ins/ for FlashPlayer.plugin and get info. On Linux, run 'rpm -q flash-player' or check /usr/lib/flash-plugin/.
    Affected if The installed version is any of these: 13.0.0.241 or lower; 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
  2. Identify installed Adobe AIR version
    On Windows, open Control Panel > Programs and Features and locate 'Adobe AIR' entry to see its version. On macOS, check /Applications/ and get info on Adobe AIR.app. Alternatively, run 'reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{XXX}' on Windows to find the AIR version.
    Affected if The installed version is any of these: 14.0.0.179 or lower; 13.0.0.83; 13.0.0.111; 14.0.0.110; 14.0.0.137; 14.0.0.178
  3. Identify installed Adobe AIR SDK version
    Check the installation directory of the AIR SDK. On Windows, common paths are C:\Program Files\Adobe\AIR SDK or C:\Users\[User]\AppData\Local\Adobe\AIR. On macOS, check /Applications/Adobe\AIR\SDK or ~/AIR_SDK. Look for a file named 'version.properties' or 'README' that contains the SDK version number.
    Affected if The installed version is any of these: 14.0.0.137 or lower; 13.0.0.83; 13.0.0.111; 14.0.0.110
  4. Check if Flash Player browser plugin is enabled
    In your web browser, verify that the Flash Player plugin is active. For Firefox, go to Add-ons > Plugins and check if 'Shockwave Flash' is set to 'Always Activate' or 'Ask to Activate'. For Chrome, go to chrome://settings/content and check Flash player permissions.
    Affected if Flash Player plugin is enabled AND the version matches any of the vulnerable versions listed above

If any of Adobe Flash Player, Adobe AIR, or Adobe AIR SDK is installed with a version matching the affected list, your environment is vulnerable to 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

Upgrade to Adobe Flash Player 13.0.0.244, 15.0.0.152 (14.x/15.x), or 11.2.202.406 (Linux); upgrade Adobe AIR to 15.0.0.249 (Windows/OS X) or 15.0.0.252 (Android); consider disabling Flash Player as an interim measure.

Recommended fix High confidence

Flash Player 13.0.0.244+ (or 15.0.0.152+ for 14.x/15.x); Adobe AIR 15.0.0.249+ (Windows/OS X) or 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 checking the version in the plugin settings.
  2. 2. Identify the installed Adobe AIR version by checking the version in the AIR settings or installed programs list.
  3. 3. For Flash Player: Download the appropriate fixed version from the Adobe Security Bulletin APSB14-21 (helpx.adobe.com/security/products/flash-player/apsb14-21.html). Windows/OS X users need 13.0.0.244 or higher (or 15.0.0.152+ for 14.x/15.x). Linux users need 11.2.202.406 or higher.
  4. 4. For Adobe AIR: Download version 15.0.0.249 or higher for Windows/OS X, or 15.0.0.252 or higher for Android.
  5. 5. For Adobe AIR SDK: Download version 15.0.0.249 or higher.
  6. 6. Close all browsers and applications using Flash Player or AIR before installing the update.
  7. 7. Install the updated version using the Adobe installer with appropriate administrator privileges.
  8. 8. Restart browsers and verify the new version is installed correctly.
Caveat Upgrading Flash Player or AIR may affect compatibility with legacy applications or web content that relies on older plugin versions; test critical workflows after upgrading

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

Fix this in Flash Player 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-0547 — 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-0547 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