dbcve.org
Enterprise Linux Desktop SupplementaryOperating system · Redhat

CVE-2015-0347

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-0350, 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 · high confidence

Memory corruption vulnerability in Adobe Flash Player allowing remote attackers to execute arbitrary code or cause denial of service. Affected versions include pre-13.0.0.281 and 14.x-17.x before 17.0.0.169 on Windows/OS X, and pre-11.2.202.457 on Linux.

MitigationUpdate Flash Player to version 13.0.0.281, 17.0.0.169, or 11.2.202.457 or later depending on platform. Given Flash EOL status, consider migrating away from Flash-based content entirely.

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
    Look for the Flash Player plugin in the browser or check for the Flash Player library file. On Linux, look for /usr/lib/flash-plugin/libflashplayer.so or /usr/lib64/flash-plugin/libflashplayer.so. On Windows, check Program Files/Adobe/Flash Player or the browser's plugins directory.
    Affected if Flash Player is present on the system
  2. Determine the installed Flash Player version
    Open a web page with Flash content and view the version through the browser's plugin information, or use the command line: rpm -q flash-plugin (RHEL), dpkg -l | grep flash (Debian/Ubuntu), or check the version in the browser's about:plugins page.
    Affected if The version returned is lower than 13.0.0.281 (Windows/OS X), lower than 17.0.0.169 (14.x-17.x Windows/OS X), or lower than 11.2.202.457 (Linux)
  3. Identify the operating system platform
    Run 'uname -a' or check /etc/os-release to determine if the system is Linux, and identify the distribution (RHEL, openSUSE, SUSE).
    Affected if The OS is one of the listed affected distributions (RHEL 5/6, openSUSE 13.1/13.2, SUSE Linux Enterprise Desktop 11/12)
  4. Compare installed version against affected version ranges
    For Windows/OS X: versions before 13.0.0.281 or between 14.0.0.0 and 17.0.0.168 are affected. For Linux: versions before 11.2.202.457 are affected. Cross-reference the installed version number with the specific versions listed in the CVE.
    Affected if The installed version matches or falls within: <= 11.2.202.451, <= 13.0.0.264, 14.0.0.125/145/176/179, 15.0.0.152/167/189/223/239/246 (Windows/OS X), or the system is RHEL 5/6, openSUSE 13.1/13.2, or SUSE with an older Flash version

A system is affected if Adobe Flash Player is installed and the installed version falls within the vulnerable version ranges: pre-13.0.0.281 or 14.x-17.x before 17.0.0.169 on Windows/OS X, or pre-11.2.202.457 on Linux.

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 Flash Player to version 13.0.0.281, 17.0.0.169, or 11.2.202.457 or later depending on platform. Given Flash EOL status, consider migrating away from Flash-based content entirely.

Recommended fix High confidence

Flash Player 17.0.0.169 or later (or 13.0.0.281 for legacy 13.x branch, or 11.2.202.457 for Linux)

  1. 1. Identify the current Flash Player version installed by navigating to https://www.adobe.com/software/flash/about/ in a browser
  2. 2. For Windows and Mac OS X: Download the latest Flash Player installer from https://get.adobe.com/flashplayer/ and install the update
  3. 3. For Linux: Update through the system package manager (e.g., yum update flash-plugin, zypper update flash-player, or apt get update followed by apt get install flashplugin-installer) to receive version 11.2.202.457 or later
  4. 4. Alternatively, download the Linux version directly from https://get.adobe.com/flashplayer/ and install the RPM/deb package
  5. 5. Restart all browsers after installation
  6. 6. Verify the installed version matches or exceeds the fixed releases: 13.0.0.281, 17.0.0.169 (for 14.x-17.x), or 11.2.202.457 (for Linux)
Caveat Adobe Flash Player reached end-of-life on December 31, 2020; consider migrating to HTML5-based alternatives as Flash is no longer supported

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

Fix this in Enterprise Linux Desktop Supplementary Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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