CVE-2015-0353
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 · uneditedAdobe 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-0352, 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 confidenceAdobe Flash Player contains a memory corruption vulnerability allowing remote attackers to execute arbitrary code or cause denial of service. The vulnerability affects versions 13.x before 13.0.0.281, 14.x-17.x before 17.0.0.169 on Windows/OS X, and versions 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<= 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= 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 -q flash-plugin (RHEL) or dpkg -l | grep -i flash (Debian/Ubuntu). On Windows, check Add/Remove Programs or the presence of Flash Player in browser plugins.Affected if Flash Player package is not found or not installed - no vulnerability present
-
Determine installed Flash Player version on LinuxRun: rpm -qi flash-plugin (RHEL) or check the file version of /usr/lib/flash-plugin/libflashplayer.so using: rpm -qf /usr/lib/flash-plugin/libflashplayer.soAffected if Package query returns no version information - Flash may not be installed
-
Compare version against affected rangesIf Flash is installed, note the version number. Compare against: 13.x before 13.0.0.281, 14.x-17.x before 17.0.0.169, or 11.2.202.451 and earlier on Linux. Any version matching or below these thresholds indicates vulnerability.Affected if Installed version falls within any of these ranges: <= 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, or any 13.x version below 13.0.0.281, or any 14.x-17.x version below 17.0.0.169 on Windows/OS X
-
Check browser plugins for embedded FlashIn browsers like Chrome (chrome://plugins), Firefox (about:plugins), or Opera (opera:plugins), locate the Flash Player entry and note the version displayed.Affected if Browser-reported Flash version matches the affected version ranges above - user is vulnerable when browsing
-
Verify Flash is enabled in browsersCheck browser plugin settings to confirm Flash Player is enabled. In Firefox, go to Add-ons > Plugins. In Chrome, visit chrome://plugins. Ensure Flash is not set to 'Never activate'.Affected if Flash Player is installed AND enabled - the vulnerability is exploitable through that browser
A system is affected if Adobe Flash Player is installed with any version before 13.0.0.281 (13.x), before 17.0.0.169 (14.x-17.x on Windows/OS X), or before 11.2.202.457 (Linux), and the Flash plugin is enabled in any 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 or later (Windows/OS X) or 11.2.202.457 or later (Linux). In enterprise environments, deploy the patch via patch management systems to all affected endpoints.
Flash Player 17.0.0.169 or later (or 13.0.0.281 for 13.x branch, or 11.2.202.457 for Linux)
- Verify current Flash Player version by navigating to 'About Flash Player' in the Adobe website or checking your system's installed programs
- Download the latest Adobe Flash Player from the official Adobe Security Bulletin APSB15-06: https://helpx.adobe.com/security/products/flash-player/apsb15-06.html
- For Linux systems: upgrade to Flash Player version 11.2.202.457 or later
- For Windows/OS X systems running 13.x branch: upgrade to version 13.0.0.281 or later
- For Windows/OS X systems running 14.x-17.x branch: upgrade to version 17.0.0.169 or later
- Alternatively, consider migrating away from Flash Player to modern HTML5-based alternatives as Adobe Flash is End-of-Life (EOL) as of December 31, 2020
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-0353 — 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-0353 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