dbcve.org
Flash PlayerApplication · Adobe

CVE-2014-0582

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
Heap-based buffer overflow in 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 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2014-0589.

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

Heap-based buffer overflow in Adobe Flash Player and AIR allows remote attackers to execute arbitrary code via unspecified vectors. The vulnerability stems from improper memory handling that corrupts heap memory, enabling code execution.

MitigationUpdate Adobe Flash Player to 13.0.0.252 or later (14.x/15.x to 15.0.0.223), 11.2.202.418 or later on Linux, and Adobe AIR/SDK to 15.0.0.356 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
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. Check Adobe Flash Player version
    Visit the Adobe version check page at https://helpx.adobe.com/flash-player.html or check the Flash Player DLL file properties (npctrl.dll, pepflashplayer.dll, or Flash32_XX_XX_XX_XX.ocx depending on browser)
    Affected if The installed version falls within these ranges: 13.0.0.0 to 13.0.0.251, 14.0.0.0 to 14.0.0.179, 15.0.0.0 to 15.0.0.222, or 11.0.0.0 to 11.2.202.417
  2. Check Adobe AIR version
    On Windows, go to Control Panel > Programs and Features and look for Adobe AIR, or check the AIR version in the Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe AIR
    Affected if The installed version is 15.0.0.356 or lower
  3. Verify Flash Player plugin is enabled
    In Internet Explorer, go to Manage Add-ons > Shockwave Flash Object; in Chrome, go to chrome://plugins and confirm Flash is enabled; in Firefox, go to Add-ons > Plugins and check Shockwave Flash status
    Affected if Flash Player plugin is enabled and the version is in any of the affected ranges listed above
  4. Check for vulnerable AIR SDK installation
    If you are a developer using Adobe AIR SDK, check the SDK version by reviewing the README or version file in the AIR SDK installation directory
    Affected if AIR SDK version is 15.0.0.356 or lower

You are affected if Adobe Flash Player version is in the vulnerable ranges (13.0.x before 13.0.0.252, 14.0.x before 14.0.0.180, 15.0.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.

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 13.0.0.252 or later (14.x/15.x to 15.0.0.223), 11.2.202.418 or later on Linux, and Adobe AIR/SDK to 15.0.0.356 or later.

Recommended fix High confidence

Flash Player 13.0.0.252+, 15.0.0.223+, or 11.2.202.418+ (Linux); Adobe AIR 15.0.0.356+

  1. 1. Identify which Adobe Flash Player or AIR version is currently installed on the system
  2. 2. For Flash Player 13.x: upgrade to version 13.0.0.252 or later
  3. 3. For Flash Player 14.x/15.x: upgrade to version 15.0.0.223 or later
  4. 4. For Flash Player 11.x (Linux): upgrade to version 11.2.202.418 or later
  5. 5. For Adobe AIR: upgrade to version 15.0.0.356 or later
  6. 6. For Adobe AIR SDK/Compiler: upgrade to version 15.0.0.356 or later
  7. 7. Verify the installed version matches or exceeds the fixed version after upgrade
  8. 8. Remove Flash Player and AIR from systems where they are no longer needed, as Adobe reached end-of-life for these products in December 2020
Caveat Adobe Flash Player and AIR reached end-of-life in December 2020 and no longer receive security updates; migrating to alternative technologies (HTML5, etc.) is recommended

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

Fix this in Flash Player Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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