dbcve.org
Enterprise Linux Desktop SupplementaryOperating system · Redhat

CVE-2015-0360

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-0354, CVE-2015-0355, 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. Exploitable via unspecified vectors through malformed content.

MitigationUpgrade Adobe Flash Player to version 13.0.0.281 or later (17.0.0.169 for 14.x-17.x branch on Windows/OS X, 11.2.202.457 for Linux). If immediate patching is not feasible, disable Flash Player in browsers or implement network-level content filtering to block malicious Flash content.

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. Verify Adobe Flash Player is installed
    On Linux, run 'rpm -qa | grep -i flash' or 'dpkg -l | grep -i flash' to list installed Flash packages. In browsers, navigate to 'chrome://plugins' (Chrome) or 'about:addons' (Firefox) to list installed plugins.
    Affected if No Flash package or plugin found means the system is not affected.
  2. Determine the exact Flash Player version
    Check the version file in the plugin directory (typically /usr/lib/flash-plugin/ or /usr/lib64/flash-plugin/). Alternatively, in a browser, visit 'https://helpx.adobe.com/flash-player.html' or check the Flash Player entry in the browser's plugin list.
    Affected if A version number is displayed that falls within the affected ranges.
  3. Compare installed version to affected ranges
    For RHEL/SLES/OpenSUSE systems, compare your installed version to: versions before 13.0.0.281, 14.x-17.x before 17.0.0.169, or Linux versions before 11.2.202.457. For the specific listed versions (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), note that these are all vulnerable.
    Affected if Your installed version matches any of the listed vulnerable versions or is earlier than the fixed versions.
  4. Confirm Flash is enabled in browsers
    Check each installed browser (Chrome, Firefox, etc.) for the Flash Player plugin status. In Firefox, go to 'Tools > Add-ons > Plugins'. In Chrome, go to 'chrome://settings/content'. Ensure Flash is not set to 'Never activate' or disabled.
    Affected if Flash Player is installed AND enabled in any browser - the vulnerability is present if the version is affected.
  5. Check for bundled Flash in third-party applications
    Some applications bundle their own Flash runtime (for example, Google Chrome includes an internal Flash). Check the application's version or bundled components. For Chrome, navigate to 'chrome://components' to see the internal Flash version.
    Affected if A bundled Flash version is present and falls within the affected ranges.

Your environment is affected if Adobe Flash Player is installed with a version matching any of the listed vulnerable versions or below the fixed thresholds (13.0.0.281, 17.0.0.169, or 11.2.202.457), and the plugin is enabled in any browser.

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 (17.0.0.169 for 14.x-17.x branch on Windows/OS X, 11.2.202.457 for Linux). If immediate patching is not feasible, disable Flash Player in browsers or implement network-level content filtering to block malicious Flash content.

Recommended fix High confidence

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

  1. 1. Identify the installed Adobe Flash Player version on the target system by navigating to https://helpx.adobe.com/flash-player.html or checking the system's installed programs
  2. 2. For Linux systems, upgrade to Adobe Flash Player 11.2.202.457 or later
  3. 3. For Windows/OS X systems with Flash Player 13.x, upgrade to version 13.0.0.281 or later
  4. 4. For Windows/OS X systems with Flash Player 14.x-17.x, upgrade to version 17.0.0.169 or later
  5. 5. After upgrading, verify the new version by visiting the Adobe version check page
  6. 6. Restart any affected browsers to ensure the new Flash Player plugin is loaded
Caveat Adobe Flash Player reached end-of-life on December 31, 2020; consider migrating away from Flash-based content as modern browsers have disabled or removed Flash support

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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