CVE-2015-0349
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 · uneditedUse-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-0351, CVE-2015-0358, and CVE-2015-3039.
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 · moderate confidenceUse-after-free vulnerability in Adobe Flash Player allowing arbitrary code execution. The flaw occurs when the software attempts to access memory after it has been freed, enabling attackers to manipulate memory and execute malicious code.
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, check for the presence of Flash Player plugins in common browser plugin directories (e.g., /usr/lib/flash-plugin, /usr/lib64/flash-plugin, ~/.mozilla/plugins). On Windows, check Program Files for Adobe folders or check browser plugin lists.Affected if Adobe Flash Player software is found on the system
-
Identify the installed Flash Player versionOn Linux, run 'rpm -q flash-plugin' for RHEL/CentOS, 'zypper se flash' for SUSE/openSUSE, or check the libflashplayer.so file version. On Windows, right-click the Flash Player DLL file in the Adobe installation folder and view Properties > Details for the version number.Affected if The version cannot be determined or the software is present but version info is inaccessible
-
Compare your installed version against affected rangesIf installed version is 13.x: check if it is 13.0.0.264 or earlier. If installed version is 14.x: check if it matches 14.0.0.125, 145, 176, or 179. If installed version is 15.x: check if it matches 15.0.0.152, 167, 189, 223, 239, or 246. If installed version is 16.x: check if it matches 16.0.0.235. For RHEL/SUSE supplementary versions: check if the system has the affected 5.0, 6.0, 6.6.z, 11.0, 12.0, 13.1, or 13.2 releases with Flash bundled.Affected if The installed version matches any of the specific versions listed or is 13.0.0.264 or earlier
-
Verify if Flash Player is enabled in browsersCheck browser settings (Chrome: chrome://plugins, Firefox: Add-ons > Plugins) to confirm if the Flash Player plugin is enabled and allowed to run. Also check if any browser plugins directory contains the Flash Player NPAPI or PPAPI plugin files.Affected if Flash Player is installed with an affected version AND the plugin is enabled in any web browser
A user is affected if they have an affected version of Adobe Flash Player installed (13.0.0.264 or earlier, or any of the listed 14.x, 15.x, or 16.x versions) and the plugin is enabled in their browser.
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 version 13.0.0.281, 17.0.0.169, or 11.2.202.457 (or later) depending on the platform. Alternatively, remove or disable Flash Player if not required.
Flash Player 13.0.0.281 or later (13.x branch); Flash Player 17.0.0.169 or later (14.x-17.x branch); Flash Player 11.2.202.457 or later (Linux)
- Identify the currently installed Adobe Flash Player version by navigating to 'about:plugins' in the browser or checking 'Add/Remove Programs'
- For Windows/OS X systems: If running Flash Player 13.x, upgrade to version 13.0.0.281 or later
- For Windows/OS X systems: If running Flash Player 14.x through 17.x, upgrade to version 17.0.0.169 or later
- For Linux systems: Upgrade to Flash Player version 11.2.202.457 or later
- Download the appropriate installer from the official Adobe security bulletin at https://helpx.adobe.com/security/products/flash-player/apsb15-06.html
- Close all web browsers and running applications that use Flash Player
- Run the Flash Player installer with administrative privileges
- Verify the installed version matches the target fixed version after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0349 — 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-0349 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