CVE-2015-5132
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 18.0.0.232 on Windows and OS X and before 11.2.202.508 on Linux, Adobe AIR before 18.0.0.199, Adobe AIR SDK before 18.0.0.199, and Adobe AIR SDK & Compiler before 18.0.0.199 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-5131 and CVE-2015-5133.
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 and Adobe AIR allowing attackers to execute arbitrary code via unspecified vectors. Affects Flash Player versions before 18.0.0.232 (Windows/OS X) and before 11.2.202.508 (Linux), and Adobe AIR/SDK versions before 18.0.0.199.
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<= 18.0.0.209<= 11.2.202.491= 11.4<= 18.0.0.180<= 18.0.0.180<= 18.0.0.180CVSS 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 Windows or macOSOpen the Adobe Flash Player Settings manager (right-click on any Flash content or go to about:plugins in browser), or check the file version of npap.dll or Flash32_*.ocx in the browser plugins directory. Alternatively, visit Adobe's version check page at https://www.adobe.com/software/flash/about/Affected if The displayed version is 18.0.0.209 or earlier on Windows/OS X, or 11.2.202.491 or earlier on Linux
-
Check Adobe Flash Player version on LinuxOpen a terminal and run: rpm -q flash-player or dpkg -l | grep flash, or check the version listed in the browser's about:plugins page for the Flash pluginAffected if The version is 11.2.202.491 or earlier
-
Check Adobe AIR versionOn Windows, open Programs and Features (or Add/Remove Programs) and look for Adobe AIR in the list. On macOS, check /Applications for Adobe AIR. Run 'air -version' from command line if AIR is installed, or check the AIR runtime version in the registry or application metadataAffected if The version is 18.0.0.180 or earlier, or the SDK/Compiler version is 18.0.0.180 or earlier
-
Check for Flash Player presence on OpenSUSE Evergreen 11.4On an OpenSUSE 11.4 system, run 'rpm -qa | grep -i flash' or 'zypper se flash' to list installed Flash packagesAffected if Any Adobe Flash Player package is installed on OpenSUSE 11.4 (this distribution ships older vulnerable versions)
You are affected if Adobe Flash Player version is 18.0.0.209 or earlier (Windows/OS X) or 11.2.202.491 or earlier (Linux), or Adobe AIR/SDK version is 18.0.0.180 or earlier.
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 18.0.0.232 or later (Windows/OS X) or 11.2.202.508 or later (Linux), and Adobe AIR/SDK to version 18.0.0.199 or later. Consider removing Flash Player if no longer required.
Flash Player 18.0.0.232 (Windows/OS X) or 11.2.202.508 (Linux); AIR 18.0.0.199; AIR SDK 18.0.0.199; AIR SDK & Compiler 18.0.0.199
- Identify the currently installed Adobe Flash Player or AIR version by navigating to About Flash Player (right-click on SWF content) or checking the system-installed version
- For Windows/OS X: Download Adobe Flash Player 18.0.0.232 from the official Adobe security bulletin (apsb15-19) or adobe.com
- For Linux: Download Flash Player 11.2.202.508 from the official Adobe security bulletin or adobe.com
- For AIR applications: Download and install AIR 18.0.0.199 or AIR SDK 18.0.0.199 from the official Adobe security bulletin or adobe.com
- Close all browser instances and any applications using Flash Player or AIR
- Run the installer with appropriate administrator privileges
- Verify the installation was successful by checking the updated version number
- Restart any affected browsers or applications
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-5132 — 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-5132 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