CVE-2015-3084
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 by leveraging an unspecified "type confusion," a different vulnerability than CVE-2015-3077 and CVE-2015-3086.
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 confidenceAdobe Flash Player and Adobe AIR contain a type confusion vulnerability that allows attackers to execute arbitrary code. The vulnerability affects specific versions across Windows, OS X, and Linux platforms, including the AIR SDK and Compiler components.
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.475<= 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<= 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.
-
Identify installed Adobe Flash Player versionOpen a browser and navigate to a page that displays Flash Player information, or check the version through your system's installed programs list. On Windows, you can also check the registry key under HKLM\SOFTWARE\Macromedia\FlashPlayer or HKLM\SOFTWARE\Adobe\FlashPlayerAffected if The installed version matches any of these: 11.2.202.475 or earlier for 11.x; 13.0.0.264 or earlier for 13.x; or exactly 14.0.0.125, 14.0.0.145, 14.0.0.176, or 14.0.0.179; or exactly 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
-
Identify installed Adobe AIR versionCheck the installed version through your system's list of installed programs or applications. On Windows, look in Add/Remove Programs for Adobe AIR. On Mac, check /Library/Application Support/Adobe/AIR or the Applications folder.Affected if The installed Adobe AIR version is 17.0.0.144 or earlier
-
Identify installed Adobe AIR SDK versionLocate the AIR SDK installation directory and check the version information file, typically found in the SDK's root folder or in the release notes accompanying the SDK.Affected if The installed Adobe AIR SDK version is 17.0.0.144 or earlier
-
Check if Flash Player ActiveX control is in useIf this is a Windows system using Internet Explorer, verify the ActiveX version by checking the FlashOCX component version in the Windows system directory or via registry under HKLM\SOFTWARE\Macromedia\FlashPlayer\SafeVersionsAffected if The ActiveX Flash Player version matches any of the affected versions listed in the Flash Player range
You are affected if any installed Adobe Flash Player version, Adobe AIR version, or Adobe AIR SDK version falls within or matches the specified vulnerable versions and ranges.
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 · scopedUpgrade Adobe Flash Player to version 13.0.0.289, 17.0.0.188, or later; Adobe AIR and AIR SDK to 17.0.0.172 or later; and Linux Flash Player to 11.2.202.460 or later.
Flash Player 13.0.0.289+ (13.x), 17.0.0.188+ (14.x-17.x), 11.2.202.460+ (Linux 11.x); AIR/AIR SDK 17.0.0.172+
- Identify the affected Adobe product (Flash Player, AIR, AIR SDK, or AIR SDK & Compiler) currently installed
- Determine the specific version family (11.x, 13.x, 14.x-17.x for Flash Player; or AIR/AIR SDK versions)
- For Flash Player 11.x on Linux: upgrade to version 11.2.202.460 or later
- For Flash Player 13.x: upgrade to version 13.0.0.289 or later
- For Flash Player 14.x through 17.x on Windows or OS X: upgrade to version 17.0.0.188 or later
- For Adobe AIR: upgrade to version 17.0.0.172 or later
- For Adobe AIR SDK: upgrade to version 17.0.0.172 or later
- For Adobe AIR SDK & Compiler: upgrade to version 17.0.0.172 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3084 — 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-3084 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