CVE-2015-3104
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 · uneditedInteger overflow in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466 on Linux, Adobe AIR before 18.0.0.144 on Windows and before 18.0.0.143 on OS X and Android, Adobe AIR SDK before 18.0.0.144 on Windows and before 18.0.0.143 on OS X, and Adobe AIR SDK & Compiler before 18.0.0.144 on Windows and before 18.0.0.143 on OS X 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 confidenceInteger overflow vulnerability in Adobe Flash Player and AIR allows remote attackers to execute arbitrary code via unspecified vectors. The vulnerability affects multiple versions across Windows, OS X, and Linux platforms.
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<= 17.0.0.144<= 17.0.0.172all versions<= 17.0.0.172<= 17.0.0.172<= 11.2.202.460<= 13.0.0.289= 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.246CVSS 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 Adobe Flash Player version on WindowsOpen Add or Remove Programs and locate Adobe Flash Player, or check the NPSWF32.dll file version in the browser plugins directory (typically C:\Windows\System32\Macromed\Flash\ for IE/Chromium, or the browser's plugin folder)Affected if The installed version is 11.2.202.460 or earlier, 13.0.0.289 or earlier, or exactly 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, or 15.0.0.246
-
Check Adobe Flash Player version on Mac OS XNavigate to /Library/Internet Plug-Ins/ and check the Flash Player.plugin version info, or check the library file version using the Finder Get Info optionAffected if The installed version matches any of the vulnerable versions listed for Windows (11.2.202.460 or earlier, 13.0.0.289 or earlier, or the specific 14.x or 15.x versions listed)
-
Check Adobe Flash Player version on LinuxOpen a terminal and run 'rpm -q flash-player' or 'dpkg -l | grep flash', or check the libflashplayer.so file version in the browser plugins directory (/usr/lib/flash-plugin/ or ~/.mozilla/plugins/)Affected if The installed version is 11.2.202.460 or earlier (Linux Flash Player was discontinued after 11.2)
-
Check Adobe AIR version on WindowsOpen Add or Remove Programs and locate Adobe AIR, or check the AIR version in the Adobe AIR directory (typically C:\Program Files\Adobe\AIR\)Affected if The installed version is 17.0.0.144 or earlier, or 17.0.0.172 or earlier
-
Check Adobe AIR version on Mac OS XOpen System Information or check /Applications/Adobe AIR Installer.app contents for the version, or use 'ls /Applications | grep -i air'Affected if The installed version is 17.0.0.144 or earlier, or 17.0.0.172 or earlier
-
Check if running on Google AndroidCheck the device settings under Settings > About Phone/Tablet > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The device is running any version of Android and has Adobe Flash Player installed (Adobe Flash Player was bundled on some Android devices and is vulnerable on all Android versions)
A user is affected if Adobe Flash Player or Adobe AIR is installed with any version listed in the affected ranges (including all versions on Android devices), and the vulnerable software is actively being used in the browser or as an application.
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.292 or 18.0.0.160 and later, or update Adobe AIR to 18.0.0.144/18.0.0.143 or later. Consider removing Flash Player if no longer required.
Flash Player: 13.0.0.292, 18.0.0.160 (Windows/OS X), 11.2.202.466 (Linux) | Adobe AIR: 18.0.0.144 (Windows), 18.0.0.143 (OS X/Android) | Adobe AIR SDK: 18.0.0.144 (Windows), 18.0.0.143 (OS X)
- 1. Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the player or checking the system plugin
- 2. For Windows/OS X: Upgrade Flash Player to version 13.0.0.292 or 18.0.0.160 (14.x-18.x users) via adobe.com get.adobe.com/flashplayer
- 3. For Linux: Upgrade Flash Player to version 11.2.202.466 via adobe.com or your Linux package manager
- 4. For Adobe AIR (Windows): Upgrade to version 18.0.0.144
- 5. For Adobe AIR (OS X/Android): Upgrade to version 18.0.0.143
- 6. For Adobe AIR SDK: Upgrade to 18.0.0.144 (Windows) or 18.0.0.143 (OS X)
- 7. Verify the installed version matches the fixed release after upgrading
- 8. Restart browsers or applications using the Flash Player plugin
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-3104 — 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-3104 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