CVE-2015-6677
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.241 and 19.x before 19.0.0.185 on Windows and OS X and before 11.2.202.521 on Linux, Adobe AIR before 19.0.0.190, Adobe AIR SDK before 19.0.0.190, and Adobe AIR SDK & Compiler before 19.0.0.190 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-5575, CVE-2015-5577, CVE-2015-5578, CVE-2015-5580, CVE-2015-5582, and CVE-2015-5588.
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 allowing arbitrary code execution or denial of service via unspecified vectors. Affects Flash Player versions before 18.0.0.241/19.0.0.185 on Windows/OS X, before 11.2.202.521 on Linux, and AIR versions before 19.0.0.190.
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<= 11.2.202.508<= 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.246<= 18.0.0.199<= 18.0.0.143<= 18.0.0.199<= 18.0.0.180all versionsCVSS 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 Internet Explorer or any browser with Flash plugin, navigate to https://helpx.adobe.com/flash-player.html, or enter 'about:flash' in Internet Explorer address bar, or open Control Panel > Programs > Flash PlayerAffected if Version displayed is 15.0.0.152, 15.0.0.167, 15.0.0.189, 15.0.0.223, 15.0.0.239, 15.0.0.246, 14.0.0.125, 14.0.0.145, 14.0.0.176, 14.0.0.179, 13.0.0.289 or earlier, or 11.2.202.508 or earlier on Windows/OS X
-
Check Adobe Flash Player version on LinuxOpen a browser with the NPAPI Flash plugin and navigate to the Adobe Flash Player Help page, or run 'rpm -q flash-plugin' or check /usr/lib/flash-plugin directory for version filesAffected if Version is 11.2.202.508 or earlier on Linux systems
-
Check Adobe AIR version on Windows or macOSOpen Windows Control Panel > Programs and Features, look for Adobe AIR entry, or run 'adb shell pm list packages' on Android to check for Adobe AIR installationAffected if Adobe AIR version is 18.0.0.199 or earlier, or 18.0.0.143 or earlier, or any version on Android devices
-
Check Adobe AIR SDK versionLocate the AIR SDK installation directory and open the readme.txt or VERSION file, or check the SDK version via command line if availableAffected if AIR SDK version is 18.0.0.199 or earlier, or AIR SDK & Compiler version is 18.0.0.180 or earlier
User is affected if Adobe Flash Player (any version listed as vulnerable on Windows/OS X/Linux), Adobe AIR, Adobe AIR SDK, or Adobe AIR SDK & Compiler is installed at any of the specified vulnerable versions, or Adobe AIR is present on any Android device.
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.241+ (Windows/OS X) or 11.2.202.521+ (Linux), and Adobe AIR to 19.0.0.190+. Remove Flash if unnecessary given its end-of-life status.
Flash Player 18.0.0.241+ (or 19.0.0.185+), AIR 19.0.0.190+, Linux Flash Player 11.2.202.521+
- Identify the installed Adobe Flash Player version by navigating to 'About Flash Player' in the right-click menu or visiting the version check page
- For Windows/OS X: Download and install Flash Player 18.0.0.241 or later (or 19.0.0.185 or later for the 19.x branch) from the official Adobe website
- For Linux: Download and install Flash Player 11.2.202.521 or later from the official Adobe website
- For Adobe AIR: Upgrade to version 19.0.0.190 or later
- For Adobe AIR SDK: Upgrade to version 19.0.0.190 or later
- For Adobe AIR SDK & Compiler: Upgrade to version 19.0.0.190 or later
- For Android: Upgrade to the latest available Adobe AIR for Android from Google Play Store or Adobe
- Restart any affected applications (browsers) after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6677 — 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-6677 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