dbcve.org
Enterprise Linux Desktop SupplementaryOperating system · Redhat

CVE-2015-3039

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-0351, and CVE-2015-0358.

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

Use-after-free vulnerability in Adobe Flash Player allows attackers to execute arbitrary code via unspecified vectors. Affected versions are before 13.0.0.281 and 14.x through 17.x before 17.0.0.169 on Windows/OS X, and before 11.2.202.457 on Linux. This is a memory corruption bug where freed memory is accessed after deallocation, enabling code execution.

MitigationUpdate Adobe Flash Player to the patched versions (13.0.0.281, 17.0.0.169, or 11.2.202.457 depending on platform) or remove Flash Player entirely if unnecessary, as it is end-of-life.

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
    On Windows: Look in C:\Windows\System32\Macromed\Flash for the Flash Player files, or check the registry key HKLM\SOFTWARE\Macromedia\FlashPlayer. On Linux: Run 'rpm -qa | grep -i flash' or 'dpkg -l | grep -i flash' to list installed flash packages. On Mac: Check /Library/Internet Plug-Ins/ for Flash Player.plugin
    Affected if Adobe Flash Player is found installed on the system
  2. Determine the installed Flash Player version
    On Windows: Read the version from the FlashPlayerPlugin_*.exe file in the browser plugins folder, or query the registry value 'Version' under HKLM\SOFTWARE\Macromedia\FlashPlayer. On Linux: Run 'rpm -q flash-plugin' or check the package version with your package manager. For browser plugins, navigate to 'about:plugins' in Firefox or 'chrome://plugins' in Chrome to list the Flash Player version
    Affected if The version cannot be determined or the version number is below the fixed releases (17.0.0.169 for Windows/OS X, 13.0.0.281 for older major versions, or 11.2.202.457 for Linux)
  3. Verify browser plugin presence
    Check installed browser plugins: In Firefox, type 'about:plugins' in the address bar and look for 'Shockwave Flash'. In Chrome, type 'chrome://plugins' and check for Flash. In Internet Explorer, check Manage Add-ons for 'Shockwave Flash Object'. Note which browsers have Flash enabled
    Affected if Any browser has Flash Player plugin enabled and the version is in the affected range
  4. Check Red Hat Enterprise Linux supplementary packages
    If using RHEL with supplementary repos, run 'rpm -qa | grep -i flash' to check for packages like 'flash-plugin' from rhn or supplementary channels. Also check 'yum list installed flash-plugin'
    Affected if The flash-plugin package version is earlier than 11.2.202.457
  5. Check OpenSUSE or SUSE systems
    On OpenSUSE (13.1, 13.2): Run 'rpm -q libflashplayer' or check via YaST package manager. On SUSE: Run 'rpm -qa | grep -i flash' for 'flash-player' or 'flash-plugin' packages
    Affected if Flash Player packages are installed with versions matching the affected version ranges listed in the CVE

The system is affected if Adobe Flash Player is installed with any version below 17.0.0.169 (Windows/OS X), below 13.0.0.281 (older major versions), or below 11.2.202.457 (Linux), or if any browser has a vulnerable Flash plugin enabled.

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 the patched versions (13.0.0.281, 17.0.0.169, or 11.2.202.457 depending on platform) or remove Flash Player entirely if unnecessary, as it is end-of-life.

Recommended fix High confidence

Upgrade to Flash Player 17.0.0.169 (or 13.0.0.281 for 13.x, or 11.2.202.457 for Linux 11.2.x)

  1. Identify the currently installed Adobe Flash Player version by navigating to about:flash (in Firefox) or checking the system information
  2. Access the Adobe security bulletin at https://helpx.adobe.com/security/products/flash-player/apsb15-06.html to obtain the correct fixed version for your platform and branch
  3. Download the appropriate patched Flash Player installer for your operating system (Windows, OS X, or Linux)
  4. Uninstall the current vulnerable Adobe Flash Player version from the system
  5. Install the downloaded patched Flash Player version (17.0.0.169 for 14.x-17.x on Windows/OS X, 13.0.0.281 for 13.x, or 11.2.202.457 for 11.2.x on Linux)
  6. Restart any browsers and verify the Flash Player version matches the patched release
Caveat Adobe Flash Player is deprecated and no longer supported as of end-of-life; consider migrating away from Flash-based content

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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