dbcve.org
Enterprise Linux Desktop SupplementaryOperating system · Redhat

CVE-2015-0352

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-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

Adobe Flash Player contains a memory corruption vulnerability allowing attackers to execute arbitrary code or cause a denial of service. This is a critical severity flaw affecting specific versions across Windows, OS X, and Linux platforms prior to the patched releases (13.0.0.281, 17.0.0.169, and 11.2.202.457 respectively).

MitigationUpdate Adobe Flash Player to version 13.0.0.281 or later (17.0.0.169 for 14.x-17.x on Windows/OS X, 11.2.202.457 for Linux) to remediate this vulnerability; alternatively, disable or remove Flash Player if unused.

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. Check if Adobe Flash Player is installed
    Windows: Open a browser and navigate to 'about:flash' or check Add/Remove Programs. Linux: Run 'rpm -q flash-player' (RHEL) or 'dpkg -l | grep flash' (Debian-based). Mac OS X: Check /Library/Application Support/Adobe/Flash Player or use System Preferences.
    Affected if Flash Player is installed on the system
  2. Identify the installed Flash Player version number
    Windows: In browser, go to 'about:flash' which displays version. Linux: Run 'rpm -qi flash-player' or check the package version. macOS: Right-click Flash Player installer in Applications > Get Info.
    Affected if Version is 13.0.0.264 or earlier, OR matches any of: 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
  3. Check if the Flash Player browser plugin is enabled
    Windows/Linux: In browser settings, check Manage Add-ons for 'Shockwave Flash Object' or 'Adobe Flash Player' plugin status. Chrome: Navigate to chrome://plugins and locate Flash.
    Affected if The Flash plugin is enabled in any web browser on the system
  4. For RHEL/SUSE systems, verify flash-player package version
    RHEL: Run 'rpm -qa | grep -i flash' or check via yum/ PackageKit. SUSE: Run 'rpm -qa | grep flash-player' or check via YaST. openSUSE: Run 'rpm -qa | grep flash'.
    Affected if The flash-player package version matches the vulnerable versions listed in the CVE for the respective distribution

A user is affected if Adobe Flash Player (or the flash-player package on Linux) is installed with a version matching any of the vulnerable versions listed in this CVE, and the Flash plugin is enabled in a 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

Update Adobe Flash Player to version 13.0.0.281 or later (17.0.0.169 for 14.x-17.x on Windows/OS X, 11.2.202.457 for Linux) to remediate this vulnerability; alternatively, disable or remove Flash Player if unused.

Recommended fix High confidence

Minimum fixed versions: Linux Flash Player 11.2.202.457+, Windows/OS X 13.x to 13.0.0.281+, or 14.x-17.x to 17.0.0.169+

  1. 1. Identify the currently installed Adobe Flash Player version on the system.
  2. 2. For Linux systems: upgrade to Flash Player version 11.2.202.457 or later.
  3. 3. For Windows/OS X systems on 13.x branch: upgrade to version 13.0.0.281 or later.
  4. 4. For Windows/OS X systems on 14.x-17.x branch: upgrade to version 17.0.0.169 or later.
  5. 5. Verify the installation of the patched version by checking the Flash Player About page.
  6. 6. Alternatively, remove Adobe Flash Player entirely if no longer needed, as it reached end-of-life in December 2020.
Caveat Adobe Flash Player reached end-of-life in December 2020; consider migrating to HTML5 or alternative technologies rather than applying this 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
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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