dbcve.org
Enterprise Linux Desktop SupplementaryOperating system · Redhat

CVE-2015-0350

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-0352, CVE-2015-0353, CVE-2015-0354, 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 · moderate confidence

Adobe Flash Player contains a memory corruption vulnerability allowing remote attackers to execute arbitrary code or cause a denial of service. The vulnerability affects multiple version ranges across Windows, OS X, and Linux platforms and is exploitable via unspecified vectors, likely through malicious SWF content loaded in the browser.

MitigationUpdate Adobe Flash Player to version 13.0.0.281, 17.0.0.169, or 11.2.202.457 (or later) for the respective platform, or remove Flash Player if unnecessary.

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. Identify if Adobe Flash Player is installed
    Check for the Flash Player plugin in browsers or the system. On Linux systems, look for /usr/lib/flash-plugin or /usr/lib64/flash-plugin directories. On Windows, check Program Files for Adobe/Flash Player or the browser's plugin directory.
    Affected if Adobe Flash Player is present on the system
  2. Determine the installed Flash Player version number
    Open a web browser and navigate to a Flash version detection page (such as about:flash in some browsers, or use an online Flash version checker). Alternatively, on Linux check the version file in the Flash plugin directory or run 'rpm -q flash-plugin' on Red Hat systems.
    Affected if The detected version matches any of the affected versions listed in the CVE advisory
  3. Compare installed version against affected version ranges
    The affected versions are: Adobe Flash Player 11.2.202.451 and earlier versions in the 11.x branch; 13.0.0.264 and earlier in the 13.x branch; versions 14.0.0.125, 14.0.0.145, 14.0.0.176, and 14.0.0.179 in the 14.x branch; versions 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.239, and 15.0.0.246 in the 15.x branch. Compare your installed version to this list.
    Affected if The installed version is exactly one of the listed versions or falls within the <= thresholds for the 11.x and 13.x branches
  4. Check if Flash Player browser plugin is enabled
    In the web browser, navigate to about:plugins (for Firefox/Chrome legacy) or check the browser's extensions/add-ons manager to see if the Shockwave Flash plugin is enabled and active.
    Affected if The Flash plugin is present and enabled in any web browser

A system is affected by this CVE if Adobe Flash Player is installed, enabled, and the installed version matches any of the specific versions or falls at or below the thresholds (11.2.202.451 or 13.0.0.264) listed in the affected products.

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, 17.0.0.169, or 11.2.202.457 (or later) for the respective platform, or remove Flash Player if unnecessary.

Recommended fix High confidence

Flash Player 11.2.202.457 (Linux) / 13.0.0.281 (13.x) / 17.0.0.169 (14.x-17.x)

  1. Identify the installed Flash Player version and operating system (Linux, Windows, or OS X)
  2. For Linux systems: Upgrade Adobe Flash Player to version 11.2.202.457 or later
  3. For Windows/OS X systems running 13.x: Upgrade to version 13.0.0.281 or later
  4. For Windows/OS X systems running 14.x-17.x: Upgrade to version 17.0.0.169 or later
  5. Alternatively, consider migrating away from Flash Player to HTML5 video support as Adobe Flash is end-of-life
  6. Verify the installed version after upgrade matches the target fixed version
Caveat Adobe Flash Player is deprecated and reached end-of-life on December 31, 2020; consider migrating to HTML5-based alternatives

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

Fix this in Enterprise Linux Desktop Supplementary Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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