CVE-2015-3090
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.289 and 14.x through 17.x before 17.0.0.188 on Windows and OS X and before 11.2.202.460 on Linux, Adobe AIR before 17.0.0.172, Adobe AIR SDK before 17.0.0.172, and Adobe AIR SDK & Compiler before 17.0.0.172 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-3078, CVE-2015-3089, and CVE-2015-3093.
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. Affects specific versions across Windows, OS X, and Linux platforms. Exploitation requires user interaction (e.g., visiting malicious webpage).
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<= 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= 16.0.0.235<= 17.0.0.144<= 17.0.0.144<= 17.0.0.144CVSS 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 Flash Player version in browserVisit a website that displays the Flash Player version (e.g., adobe.com/software/flash/about), or open Internet Explorer and navigate to Tools > Manage Add-ons > Shockwave Flash Object to see the versionAffected if The displayed version matches any of these: 13.0.0.264 or earlier; 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; 16.0.0.235
-
Check Adobe AIR installation version on WindowsOpen Control Panel > Programs and Features, locate Adobe AIR in the list, and note the version columnAffected if The version listed is 17.0.0.144 or earlier
-
Check Adobe AIR SDK versionIf you have the AIR SDK installed, navigate to the SDK directory and open the AIRSDKReadme.txt or check the version file included in the SDK packageAffected if The SDK version is 17.0.0.144 or earlier
-
Check if Flash Player is enabled in your browserIn your browser settings, verify whether the Flash Player plugin or extension is currently enabled (Chrome: chrome://plugins; Firefox: Add-ons > Plugins)Affected if Flash Player is enabled and the version falls within the affected ranges listed above
Your environment is affected if Adobe Flash Player is installed and enabled with a version matching the listed affected versions, or if Adobe AIR/SDK version is 17.0.0.144 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 · scopedApply vendor patches: update Flash Player to 13.0.0.289, 17.0.0.188 (Windows/OS X), or 11.2.202.460 (Linux); update AIR to 17.0.0.172 or later. Consider disabling Flash Player if unnecessary.
Flash Player 13.0.0.289+, 17.0.0.188+ (Windows/OS X), 11.2.202.460+ (Linux); Adobe AIR/SDK 17.0.0.172+
- 1. Identify the currently installed Adobe Flash Player version by navigating to 'About Flash Player' in the Help menu, or visiting 'https://helpx.adobe.com/flash-player.html'
- 2. For Flash Player 13.x users: Upgrade to version 13.0.0.289 or later from the Adobe Flash Player download center
- 3. For Flash Player 14.x through 17.x users (Windows/OS X): Upgrade to version 17.0.0.188 or later
- 4. For Flash Player 11.x users (Linux): Upgrade to version 11.2.202.460 or later
- 5. For Adobe AIR users: Upgrade to version 17.0.0.172 or later
- 6. For Adobe AIR SDK users: Upgrade to version 17.0.0.172 or later
- 7. For Adobe AIR SDK & Compiler users: Upgrade to version 17.0.0.172 or later
- 8. Restart any browser instances and verify the updated version via the Flash Player Help > About dialog
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3090 — 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-3090 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