CVE-2015-0348
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 · uneditedBuffer overflow 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.
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 confidenceBuffer overflow vulnerability in Adobe Flash Player allows attackers to execute arbitrary code via unspecified vectors. Affected versions include Flash Player before 13.0.0.281, versions 14.x through 17.x before 17.0.0.169 on Windows/OS X, and before 11.2.202.457 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= 5.0= 6.0= 5.0= 6.0= 6.6.z= 6.0<= 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= 13.1= 13.2= 11.0= 12.0= 12.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Adobe Flash Player is installedOn Linux systems, run: rpm -qa | grep -i flash (RHEL/CentOS) or dpkg -l | grep -i flash (Debian/Ubuntu) or zypper se flash (SUSE/openSUSE). On Windows, check browser plugins or C:\Windows\System32\Macromed\Flash for the Flash.ocx file.Affected if No output means Flash is not installed and the system is not affected.
-
Identify the installed Flash Player version on LinuxRun: rpm -q libflashplayer or rpm -q flash-player (RHEL/CentOS). On SUSE/openSUSE, run: rpm -q flash-player. The command returns the package name with version (e.g., flash-player-11.2.202.457).Affected if The version number returned is one of the listed affected versions or falls within the vulnerable ranges.
-
Identify Flash Player version in browsersIn any web browser, navigate to: https://helpx.adobe.com/flash-player.html or type 'about:plugins' in the address bar (Firefox) or check Chrome's chrome://plugins page to view the Flash version.Affected if The displayed Flash version matches any of the affected versions listed.
-
Verify the specific version against affected rangesCompare your installed version to: Flash Player <= 13.0.0.264, versions 14.x, 15.x, 16.x before 17.0.0.169 (Windows/OS X), or < 11.2.202.457 on Linux. Any version matching these conditions is vulnerable.Affected if Your installed version is lower than 13.0.0.281, is 14.x/15.x/16.x, or is below 11.2.202.457 on Linux.
-
Check for Red Hat supplementary channel packagesOn RHEL systems, run: yum list installed | grep -i flash or check /etc/redhat-release to confirm the RHEL version (5.x, 6.x, 6.6.z). Then query the installed Flash package version.Affected if Running RHEL 5.0, 6.0, or 6.6.z with Flash Player installed from supplementary channels.
If Adobe Flash Player is installed and its version falls within any of the affected ranges (before 13.0.0.281, any 14.x/15.x/16.x version, or below 11.2.202.457 on Linux), the environment is vulnerable to CVE-2015-0348.
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 · scopedUpdate Adobe Flash Player to the fixed versions (13.0.0.281, 17.0.0.169, or 11.2.202.457) or remove/disable Flash Player as it has reached end-of-life.
Adobe Flash Player 13.0.0.281+ (13.x), 17.0.0.169+ (14.x-17.x), or 11.2.202.457+ (Linux)
- 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' or checking the system package manager.
- 2. For Linux systems: upgrade to Adobe Flash Player 11.2.202.457 or later.
- 3. For Windows/OS X systems with version 13.x: upgrade to Adobe Flash Player 13.0.0.281 or later.
- 4. For Windows/OS X systems with version 14.x-17.x: upgrade to Adobe Flash Player 17.0.0.169 or later.
- 5. For Red Hat Enterprise Linux systems: run 'yum update flash-plugin' or 'rpm -Uvh' with the updated package from Red Hat channels.
- 6. For SUSE systems: use 'zypper update' or 'zypper in' to install the updated flash-player package.
- 7. For openSUSE systems: use 'zypper update' to fetch the patched flash-player package.
- 8. Verify the installation by checking the Flash Player version at https://www.adobe.com/software/flash/about/
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0348 — 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-0348 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