CVE-2015-3113
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 · uneditedHeap-based buffer overflow in Adobe Flash Player before 13.0.0.296 and 14.x through 18.x before 18.0.0.194 on Windows and OS X and before 11.2.202.468 on Linux allows remote attackers to execute arbitrary code via unspecified vectors, as exploited in the wild in June 2015.
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 confidenceHeap-based buffer overflow in Adobe Flash Player allowing remote arbitrary code execution via unspecified vectors. Actively exploited in the wild in June 2015, affecting unpatched versions 13.x before 13.0.0.296, 14.x-18.x before 18.0.0.194 on Windows/OS X, and before 11.2.202.468 on Linux.
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= 6.0= 6.6= 6.0= 6.0< 13.0.0.296>= 14.0.0.125, < 18.0.0.194< 11.2.202.468= 11.4= 13.1= 13.2= 12CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Adobe Flash Player is installedOn Windows, check C:\Windows\System32\Macromed\Flash\ for the Flash OCX/DLL file, or use 'Get-ItemProperty' in PowerShell for the registry key HKLM\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion. On Linux, check /usr/lib/flash-plugin/ or /opt/flash-player/ directories, or run 'rpm -q flash-player' or 'dpkg -l | grep flash'. On macOS, check /Library/Internet Plug-Ins/Flash Player.pluginAffected if Adobe Flash Player is present on the system and its version is any version prior to the patched releases (pre-13.0.0.296, pre-18.0.0.194 for versions 14.x+, or pre-11.2.202.468 for Linux). The exact vulnerable versions are: < 13.0.0.296 OR (>= 14.0.0.125 AND < 18.0.0.194) OR < 11.2.202.468 (Linux).
-
Identify the operating system versionOn Linux systems, run 'cat /etc/os-release' or 'uname -a' to determine the distribution and version. For Red Hat Enterprise Linux specifically, run 'cat /etc/redhat-release'. For SUSE, run 'cat /etc/SuSE-release' or check 'lsb_release -a'.Affected if The system is running Red Hat Enterprise Linux 6.0, 6.6 (or any 6.x variant including Desktop, Server, Workstation, or EUS), OpenSUSE 11.4, 13.1, or 13.2, or SUSE Linux Enterprise Desktop 12 that includes bundled or installed Adobe Flash Player.
-
Verify the specific Flash Player version against affected rangesCompare your installed Flash Player version number to the affected ranges. For Windows/OS X: vulnerable if version is less than 13.0.0.296 OR between 14.0.0.125 and 18.0.0.193 inclusive. For Linux: vulnerable if version is less than 11.2.202.468.Affected if The installed Flash Player version falls into any of these vulnerable ranges: < 13.0.0.296 OR >= 14.0.0.125 but < 18.0.0.194 OR < 11.2.202.468 (Linux-specific).
-
Check for Flash Player in web browsersOpen any web browser that may have Flash Player plugin enabled (Internet Explorer, Firefox, Chrome, etc.) and navigate to 'about:plugins' or 'chrome://plugins' to list all installed plugins and their versions. Alternatively, visit Adobe's version check page at https://www.adobe.com/software/flash/about/ while Flash is installed to display the exact version.Affected if Any browser has Adobe Flash Player plugin enabled with a version matching the vulnerable ranges listed above.
A system is affected if Adobe Flash Player (any browser plugin or standalone) is installed with a version less than 13.0.0.296, between 14.0.0.125 and 18.0.0.193, or less than 11.2.202.468 on Linux, or if the system runs RHEL 6.x, OpenSUSE 11.4/13.1/13.2, or SLED 12 with bundled Flash Player from the affected era.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.2.202.46813.0.0.29618.0.0.194
Immediately update Adobe Flash Player to version 18.0.0.194 or later (Windows/OS X), 11.2.202.468 or later (Linux), or 13.0.0.296 or later (version 13). Consider removing Flash Player entirely if unnecessary, as it is deprecated.
13.0.0.296, 18.0.0.194, or 11.2.202.468 (or later). Note: Adobe Flash Player reached end-of-life on December 31, 2020; upgrade to 18.0.0.194 or later and plan for removal.
- Identify all systems with Adobe Flash Player installed
- Remove Adobe Flash Player from affected systems using the appropriate package manager or uninstaller
- For Linux: sudo yum remove flash-plugin or sudo zypper remove flash-player
- For RHEL/CentOS: sudo yum remove flash-plugin or check /opt/ for Adobe removal scripts
- Verify removal by checking that Flash Player is no longer installed
- Alternatively, if Flash is required, upgrade to version 13.0.0.296, 18.0.0.194, or 11.2.202.468 (Linux) or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2015-3113 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-3113 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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