dbcve.org
Flash PlayerApplication · Adobe

CVE-2014-0558

HIGH · 10.0 CVSS v2.0 Published 2014-10-15
Fix available
A fix is available. Upgrade to after 15.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.250 and 14.x and 15.x before 15.0.0.189 on Windows and OS X and before 11.2.202.411 on Linux, Adobe AIR before 15.0.0.293, Adobe AIR SDK before 15.0.0.302, and Adobe AIR SDK & Compiler before 15.0.0.302 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2014-0564.

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 via unspecified vectors. Affected versions span multiple platforms including Windows, OS X, and Linux.

MitigationUpdate Adobe Flash Player to version 13.0.0.250/15.0.0.189 (Windows/OS X) or 11.2.202.411 (Linux), and Adobe AIR/SDK to version 15.0.0.293 or 15.0.0.302 respectively.

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.244= 13.0.0.182= 13.0.0.201= 13.0.0.206= 13.0.0.214= 13.0.0.223= 13.0.0.231= 13.0.0.241= 14.0.0.125= 14.0.0.145= 14.0.0.176= 14.0.0.179
Adobe AirApplication
Affected:<= 15.0.0.252= 13.0.0.83= 13.0.0.111= 14.0.0.110= 14.0.0.137= 14.0.0.179<= 15.0.0.249= 14.0.0.178
Adobe Air SdkApplication
Affected:<= 15.0.0.249= 13.0.0.83= 13.0.0.111= 14.0.0.110= 14.0.0.137= 14.0.0.178

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 Adobe Flash Player installation and version
    On Windows, open Add or Remove Programs and locate Adobe Flash Player; on macOS, check /Applications for Flash Player or use System Information > Software; on Linux, check the package manager or /usr/lib/flash-plugin directory
    Affected if The installed version matches any of these: 13.0.0.244 or earlier; 13.0.0.182; 13.0.0.201; 13.0.0.206; 13.0.0.214; 13.0.0.223; 13.0.0.231; 13.0.0.241; 14.0.0.125; 14.0.0.145; 14.0.0.176; 14.0.0.179
  2. Identify Adobe AIR installation and version
    On Windows, open Programs and Features or check the Adobe AIR installation directory; on macOS, check /Applications for Adobe AIR or inspect the AIR app metadata
    Affected if The installed version is 15.0.0.252 or earlier, or exactly matches: 13.0.0.83; 13.0.0.111; 14.0.0.110; 14.0.0.137; 14.0.0.178; 14.0.0.179
  3. Identify Adobe AIR SDK installation and version
    Check the local Adobe AIR SDK installation directory or examine the AIR SDK version file included in the SDK distribution
    Affected if The installed version is 15.0.0.249 or earlier, or exactly matches: 13.0.0.83; 13.0.0.111; 14.0.0.110; 14.0.0.137; 14.0.0.178
  4. Verify browser-specific Flash Player plugin versions
    In each installed web browser, navigate to the Adobe version check page or access the browser's plugin management interface to list the Flash Player version
    Affected if Any browser plugin version matches the affected Flash Player versions listed above

You are affected if any installed Adobe Flash Player, AIR, or AIR SDK version matches the specific versions or falls within the <= ranges identified in the affected product list.

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 15.0.0.252
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.250/15.0.0.189 (Windows/OS X) or 11.2.202.411 (Linux), and Adobe AIR/SDK to version 15.0.0.293 or 15.0.0.302 respectively.

Recommended fix High confidence

Flash Player 13.x -> 13.0.0.250 or later; Flash Player 14.x/15.x -> 15.0.0.189 or later; Flash Player (Linux) -> 11.2.202.411 or later; Adobe AIR -> 15.0.0.293 or later; Adobe AIR SDK -> 15.0.0.302 or later

  1. 1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click menu or visiting 'about:flash' in the browser.
  2. 2. Identify the installed Adobe AIR version from 'C:\Program Files\Adobe\Adobe AIR\versions\readme.txt' on Windows or '/Library/Application Support/Adobe/AIR' on macOS.
  3. 3. For Flash Player on Windows or OS X: Download and install the latest version from the Adobe Security Bulletin APSB14-22 (https://helpx.adobe.com/security/products/flash-player/apsb14-22.html). For Windows, ensure the installed version is >= 15.0.0.189 (or >= 13.0.0.250 for the 13.x branch).
  4. 4. For Flash Player on Linux: Ensure the installed version is >= 11.2.202.411.
  5. 5. For Adobe AIR (runtime): Download and install version >= 15.0.0.293 from the Adobe Security Bulletin APSB14-22.
  6. 6. For Adobe AIR SDK/Compiler: Download and install version >= 15.0.0.302 from the Adobe Security Bulletin APSB14-22.
  7. 7. Verify the update was successful by re-checking the version numbers in steps 1-2.
  8. 8. Restart any running browsers or applications that use Flash Player or AIR after the update.
Caveat As Adobe Flash Player has reached end-of-life and is no longer supported, consider migrating away from Flash-based content; legacy applications may require reimplementation in modern web technologies

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
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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