dbcve.org
Enterprise Linux Desktop SupplementaryOperating system · Redhat

CVE-2015-0351

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
Use-after-free vulnerability in 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 via unspecified vectors, a different vulnerability than CVE-2015-0349, CVE-2015-0358, and CVE-2015-3039.

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

Use-after-free vulnerability in Adobe Flash Player allows attackers to execute arbitrary code via unspecified vectors. The vulnerability exists in versions before 13.0.0.281 and 14.x-17.x before 17.0.0.169 on Windows/OS X, and before 11.2.202.457 on Linux.

MitigationUpgrade Adobe Flash Player to version 13.0.0.281 or later (Windows/OS X), or 11.2.202.457 or later (Linux). 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
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:<= 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= 16.0.0.235
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. Verify Adobe Flash Player is installed
    Check for the presence of Flash Player plugin. On Windows, look for npflash32.dll or similar in browser plugin directories, or check 'Add or Remove Programs'. On Linux, check for /usr/lib/flash-plugin or /usr/lib64/flash-plugin directory, or rpm -q flash-player. On Mac OS X, check /Library/Internet\ Plug-Ins/ for Flash*.plugin
    Affected if Flash Player is not present on the system, then the vulnerability does not apply.
  2. Determine the installed Flash Player version
    In a web browser with Flash, visit 'about:flash' or use a site like adobe.com/software/flash/about. On Linux, run 'rpm -q flash-player' or check the version file in /usr/lib/flash-plugin. On Windows, check the file properties of npctrl.dll or flash*.ocx in the System32 or SysWOW64 directories.
    Affected if The exact version cannot be determined, assume potentially affected.
  3. Compare version against affected ranges
    For 13.x branch: version must be >= 13.0.0.281 to be fixed; any version <= 13.0.0.264 is vulnerable. For 14.x-16.x: 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, 16.0.0.235 are specifically listed as vulnerable. For 17.x on Windows/OS X: version must be >= 17.0.0.169. For Linux: version must be >= 11.2.202.457.
    Affected if Installed version is in any of the vulnerable ranges or matches any of the specific vulnerable versions listed.
  4. Confirm operating system platform
    Identify if the system is Windows, OS X, or Linux. Run 'uname -a' on Linux/Mac, or check System Properties on Windows. This matters because Linux has a different fixed version (11.2.202.457) compared to Windows/OS X (17.0.0.169 for 17.x branch or 13.0.0.281 for 13.x branch).
    Affected if The platform is misidentified, leading to incorrect version comparison against wrong threshold.
  5. Verify Flash plugin is enabled in browsers
    Check browser settings for Flash plugin status. In Chrome, navigate to chrome://plugins. In Firefox, go to Add-ons > Plugins. Ensure Adobe Flash Player is listed as 'Enabled' or 'Always Activate'.
    Affected if Flash is installed but completely disabled in all browsers, exploitation likelihood is reduced but the vulnerable software is still present on the system.

The environment is affected if Adobe Flash Player is installed and its version matches any of the vulnerable versions listed: 13.0.0.264 or earlier, any of the specific 14.x-16.x versions enumerated, or for Windows/OS X 17.x before 17.0.0.169, or for Linux before 11.2.202.457.

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

Upgrade Adobe Flash Player to version 13.0.0.281 or later (Windows/OS X), or 11.2.202.457 or later (Linux). Alternatively, disable or remove Flash Player if not required.

Recommended fix High confidence

Flash Player 13.0.0.281+ (13.x branch), 17.0.0.169+ (14.x-17.x branch), or 11.2.202.457+ (Linux)

  1. Identify the currently installed Flash Player version by navigating to https://about:flash or checking the plugin in the browser
  2. Determine which branch of Flash Player is installed (13.x, 14.x-17.x, or 11.x for Linux)
  3. Download the appropriate fixed version from the Adobe Security Bulletin APSB15-06: https://helpx.adobe.com/security/products/flash-player/apsb15-06.html
  4. For 13.x versions: upgrade to 13.0.0.281 or later
  5. For 14.x-17.x versions: upgrade to 17.0.0.169 or later
  6. For Linux versions: upgrade to 11.2.202.457 or later
  7. Restart the browser after installation to ensure the new version is loaded
  8. Verify the installed version matches the expected fixed release
Caveat Flash Player upgrades rarely introduce breaking changes but may affect compatibility with older content; ensure critical web applications are tested after upgrade

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

Fix this in Enterprise Linux Desktop Supplementary Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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