dbcve.org
Enterprise Linux Desktop SupplementaryOperating system · Redhat

CVE-2015-0354

HIGH · 10.0 CVSS v2.0 Published 2015-04-14
Fix available
A fix is available. Upgrade to after 13.0.0.264 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.281 and 14.x through 17.x before 17.0.0.169 on Windows and OS X and before 11.2.202.457 on Linux allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-0347, CVE-2015-0350, CVE-2015-0352, CVE-2015-0353, CVE-2015-0355, CVE-2015-0360, CVE-2015-3038, CVE-2015-3041, CVE-2015-3042, and CVE-2015-3043.

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 allowing arbitrary code execution or denial of service. Affects versions before 13.0.0.281, 14.x-17.x before 17.0.0.169 on Windows/OS X, and before 11.2.202.457 on Linux.

MitigationUpdate Adobe Flash Player to version 13.0.0.281 or later, 17.0.0.169 or later for versions 14-17, or 11.2.202.457 or later for Linux. Consider removing Flash Player if no longer required, as it reached end-of-life in December 2020.

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
Enterprise Linux Desktop SupplementaryOperating system
Affected:= 5.0= 6.0
Enterprise Linux Server SupplementaryOperating system
Affected:= 5.0= 6.0
Enterprise Linux Server Supplementary EusOperating system
Affected:= 6.6.z
Enterprise Linux Workstation SupplementaryOperating system
Affected:= 6.0
Flash PlayerApplication
Affected:<= 11.2.202.451<= 13.0.0.264= 14.0.0.125= 14.0.0.145= 14.0.0.176= 14.0.0.179= 15.0.0.152= 15.0.0.167= 15.0.0.189= 15.0.0.223= 15.0.0.239= 15.0.0.246
OpensuseOperating system
Affected:= 13.1= 13.2
Suse Linux Enterprise DesktopOperating system
Affected:= 11.0= 12.0
Suse Linux Workstation ExtensionOperating system
Affected:= 12.0

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 if Adobe Flash Player is installed
    On Windows, look for 'C:\Windows\System32\Macromed\Flash\' directory or check browser plugins. On Linux, check for '/usr/lib/flash-player/' or '/usr/lib64/flash-plugin/'. On Mac, check '/Library/Application Support/Adobe/Flash Player/'
    Affected if The Flash Player plugin or player software exists on the system
  2. Determine the installed Flash Player version
    Open a browser and navigate to 'about:plugins' or visit 'https://helpx.adobe.com/flash-player.html' which displays the version. Alternatively, check the version in the Flash DLL file properties on Windows (npctrl.dll, npjp2.dll, etc.)
    Affected if The displayed version matches any of the vulnerable versions listed in the CVE (any version before 13.0.0.281, 14.x-17.x before 17.0.0.169, or Linux before 11.2.202.457)
  3. Verify the exact version number against affected ranges
    Compare your installed version string to the vulnerable versions: Flash Player 11.2.202.451 or earlier on Linux, 13.0.0.264 or earlier on Windows/OS X, or versions 14.0.0.125, 14.0.0.145, 14.0.0.176, 14.0.0.179, 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.239, 15.0.0.246
    Affected if The installed version falls within or below these specific version numbers
  4. Check if Flash Player is enabled in browsers
    In each installed browser (Chrome, Firefox, Internet Explorer, Edge), go to the plugins settings and verify if the Flash Player plugin is enabled and active
    Affected if Flash Player is installed AND enabled in any web browser, making it exploitable via malicious web content

If Adobe Flash Player is installed and its version falls below 13.0.0.281 (Windows/OS X), below 17.0.0.169 (versions 14-17), or below 11.2.202.457 (Linux), or matches any of the specific vulnerable 14.x or 15.x versions listed, the system is affected by 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 13.0.0.264
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Flash Player to version 13.0.0.281 or later, 17.0.0.169 or later for versions 14-17, or 11.2.202.457 or later for Linux. Consider removing Flash Player if no longer required, as it reached end-of-life in December 2020.

Recommended fix High confidence

Flash Player 13.0.0.281+ (Windows/OS X), 17.0.0.169+ (Windows/OS X), or 11.2.202.457+ (Linux)

  1. Identify the currently installed Adobe Flash Player version via browser or system package manager
  2. For Windows/OS X: Download the fixed Flash Player version from the Adobe security bulletin (APSB15-06) at https://helpx.adobe.com/security/products/flash-player/apsb15-06.html
  3. For Linux: Upgrade to Flash Player 11.2.202.457 or later via system package manager (e.g., zypper for openSUSE, yum/rpm for RHEL)
  4. Uninstall any existing Flash Player installations before installing the new version
  5. Install the appropriate fixed version based on your platform: 13.0.0.281+ or 17.0.0.169+ for Windows/OS X, 11.2.202.457+ for Linux
  6. Verify the installed version matches the fixed release
Caveat Ensure browser compatibility with the upgraded Flash Player version; some older browsers may not support newer Flash versions

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

Fix this in Enterprise Linux Desktop Supplementary Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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