CVE-2015-5544
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 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 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-5545, CVE-2015-5546, CVE-2015-5547, CVE-2015-5548, CVE-2015-5549, CVE-2015-5552, and CVE-2015-5553.
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 confidenceMemory corruption vulnerability in Adobe Flash Player and Adobe AIR allows remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. The flaw affects multiple product 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<= 18.0.0.180<= 18.0.0.180<= 18.0.0.180<= 18.0.0.209<= 11.2.202.491CVSS 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 OS XOpen a browser and navigate to the Adobe Flash Player version check page at about:flash, or visit the Adobe diagnostic page. Alternatively, check the file properties of npapi32.dll (Firefox) or pepflashplayer.dll (Chrome) in the browser's plugin directory.Affected if The installed version is 18.0.0.209 or earlier, or 11.2.202.491 or earlier on Linux.
-
Check Adobe Flash Player version on LinuxOpen a terminal and run the command: rpm -q flash-player or dpkg -l | grep flash, depending on the package manager. Also check /usr/lib/flash-plugin/ for the plugin file.Affected if The installed version is 11.2.202.491 or earlier.
-
Check Adobe AIR version on WindowsOpen Control Panel and look for Adobe AIR in the Programs and Features list, or check the file version of AIR.exe in the Adobe AIR installation directory (typically C:\Program Files\Adobe\Adobe AIR).Affected if The installed version is 18.0.0.180 or earlier.
-
Check Adobe AIR version on OS XOpen Finder, navigate to /Applications/Adobe AIR Application Installer, right-click and select Get Info, or check via Terminal using: ls /Applications/ | grep -i adobeAffected if The installed version is 18.0.0.180 or earlier.
-
Check Adobe AIR SDK versionInspect the AIR SDK version file (version.xml or air-sdk-version) located in the SDK installation directory, or run: adt -version if the AIR Developer Tool is available.Affected if The SDK version is 18.0.0.180 or earlier.
A user is affected if Adobe Flash Player is version 18.0.0.209 or earlier (Windows/OS X) or 11.2.202.491 or earlier (Linux), or if Adobe AIR/AIR SDK is version 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) / 11.2.202.508 or later (Linux), and Adobe AIR to version 18.0.0.199 or later. These are critical updates addressing code execution vulnerabilities.
Flash Player 18.0.0.232+ (Windows/OS X) / 11.2.202.508+ (Linux); Adobe AIR 18.0.0.199+; Adobe AIR SDK 18.0.0.199+
- Check current Adobe Flash Player version by visiting about:flash or using the Adobe version check tool
- Check current Adobe AIR/AIR SDK version in the About panel or SDK documentation
- For Flash Player: Download and install version 18.0.0.232 or later for Windows/OS X, or version 11.2.202.508 or later for Linux from https://get.adobe.com/flashplayer/
- For Adobe AIR: Download and install version 18.0.0.199 or later from https://get.adobe.com/air/
- For Adobe AIR SDK: Download and install version 18.0.0.199 or later from https://airsdk.harman.com/ (or official Adobe AIR SDK download page)
- Verify the update was successful by checking the version again
- Consult the vendor security bulletin at https://helpx.adobe.com/security/products/flash-player/apsb15-19.html for complete details
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5544 — 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-5544 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