dbcve.org
Flash PlayerApplication · Adobe

CVE-2014-0584

HIGH · 10.0 CVSS v2.0 Published 2014-11-11
Fix available
A fix is available. Upgrade to 11.2.202.418 / 13.0.0.252 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.252 and 14.x and 15.x before 15.0.0.223 on Windows and OS X and before 11.2.202.418 on Linux, Adobe AIR before 15.0.0.356, Adobe AIR SDK before 15.0.0.356, and Adobe AIR SDK & Compiler before 15.0.0.356 allow attackers to execute arbitrary code by leveraging an unspecified "type confusion," a different vulnerability than CVE-2014-0577, CVE-2014-0585, CVE-2014-0586, and CVE-2014-0590.

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

This is a type confusion vulnerability in Adobe Flash Player and Adobe AIR that allows remote attackers to execute arbitrary code via unspecified vectors. The vulnerability stems from Flash's handling of different object types, where an attacker can cause the software to misinterpret an object's type, leading to memory corruption and code execution.

MitigationUpdate Adobe Flash Player to version 13.0.0.252 or later (14.x/15.x to 15.0.0.223), and Adobe AIR to 15.0.0.356 or later. For Linux, update to 11.2.202.418 or later. Alternatively, disable or remove Flash Player if not required.

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, < 13.0.0.252>= 14.0, <= 14.0.0.179>= 15.0, < 15.0.0.223>= 11.0, < 11.2.202.418
Air SdkApplication
Affected:<= 15.0.0.356
AirApplication
Affected:<= 15.0.0.356
Air Sdk \& CompilerApplication
Affected:< 15.0.0.356

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
    Open a browser and navigate to Adobe's version check page at get.adobe.com/flashplayer/about, or inspect the Flash Player plugin in the browser's plugin list (chrome://plugins in Chrome, about:plugins in Firefox). On Windows, also check Add/Remove Programs for Adobe Flash Player entry.
    Affected if The reported version matches one of these vulnerable ranges: 13.0.0.0 through 13.0.0.251, 14.0.0.0 through 14.0.0.179, 15.0.0.0 through 15.0.0.222, or 11.0.0.0 through 11.2.202.417.
  2. Identify installed Adobe AIR version
    On Windows, open Add/Remove Programs and look for Adobe AIR. On Mac, check /Applications for Adobe AIR. The version is typically displayed in the application name or can be found in the AIR SDK if installed.
    Affected if The installed Adobe AIR version is 15.0.0.356 or lower.
  3. Identify installed Adobe AIR SDK version
    Check the AIR SDK installation directory or the version information of the AIR SDK/Compiler package. On Windows this may be under the Adobe SDK folder or within IDE installations like Flash Builder.
    Affected if The AIR SDK or AIR SDK & Compiler version is below 15.0.0.356.
  4. Verify Flash Player plugin is active in browsers
    List all browsers installed on the system and check their plugin or extension managers to confirm whether the Adobe Flash Player plugin is enabled. Common paths: Chrome address bar type chrome://plugins, Firefox use Add-ons > Plugins.
    Affected if Flash Player is installed AND enabled in any web browser on the system.

You are affected if Adobe Flash Player version falls within any of the four vulnerable ranges (13.x before 13.0.0.252, 14.x up to 14.0.0.179, 15.x before 15.0.0.223, or 11.x before 11.2.202.418) OR if Adobe AIR/SDK version is 15.0.0.356 or lower, and the Flash plugin is active in any browser.

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 11.2.202.418 / 13.0.0.252 / 15.0.0.223 or later
Fixed in 11.2.202.41813.0.0.25215.0.0.223
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.252 or later (14.x/15.x to 15.0.0.223), and Adobe AIR to 15.0.0.356 or later. For Linux, update to 11.2.202.418 or later. Alternatively, disable or remove Flash Player if not required.

Recommended fix High confidence

Flash Player: 13.0.0.252/14.0.0.180/15.0.0.223/11.2.202.418; AIR: 15.0.0.356 (depending on your branch)

  1. 1. Identify which Adobe Flash Player and/or AIR version is currently installed by checking Help > About in the Flash Player or AIR application
  2. 2. For Flash Player 11.x on Linux: upgrade to version 11.2.202.418 or later
  3. 3. For Flash Player 13.x: upgrade to version 13.0.0.252 or later
  4. 4. For Flash Player 14.x: upgrade to version 14.0.0.180 or later
  5. 5. For Flash Player 15.x: upgrade to version 15.0.0.223 or later
  6. 6. For Adobe AIR: upgrade to version 15.0.0.356 or later
  7. 7. For Adobe AIR SDK/SDK & Compiler: upgrade to version 15.0.0.356 or later
  8. 8. Verify the upgrade was successful by checking the installed version again
Caveat Flash Player reached end-of-life in December 2020; some browsers have removed Flash support entirely and may not allow installation of newer versions

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