CVE-2016-0984
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 · uneditedUse-after-free vulnerability in Adobe Flash Player before 18.0.0.329 and 19.x and 20.x before 20.0.0.306 on Windows and OS X and before 11.2.202.569 on Linux, Adobe AIR before 20.0.0.260, Adobe AIR SDK before 20.0.0.260, and Adobe AIR SDK & Compiler before 20.0.0.260 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2016-0973, CVE-2016-0974, CVE-2016-0975, CVE-2016-0982, and CVE-2016-0983.
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 confidenceUse-after-free vulnerability in Adobe Flash Player and Adobe AIR that allows remote attackers to execute arbitrary code via unspecified vectors. The flaw occurs when memory is accessed after being freed, potentially enabling attackers to control memory execution flow.
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<= 20.0.0.272<= 11.2.202.559<= 18.0.0.326<= 20.0.0.286<= 20.0.0.286<= 20.0.0.233<= 20.0.0.233<= 20.0.0.233CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\CurrentVersion, or check the file properties of NPSWF32.dll in the System32 or SysWOW64 folder.Affected if The version listed is 20.0.0.272 or earlier, 18.0.0.326 or earlier, 20.0.0.286 or earlier, or 11.2.202.559 or earlier depending on the branch.
-
Check Adobe Flash Player version on macOSOpen Finder, go to /Library/Internet Plug-Ins/, locate Flash Player.plugin, right-click and select Get Info to view the version, or run: defaults read /Library/Internet\ Plug-Ins/Flash\ Player.plugin/Contents/Info CFBundleVersionAffected if The version is 20.0.0.272 or earlier, 18.0.0.326 or earlier, 20.0.0.286 or earlier, or 11.2.202.559 or earlier depending on the branch.
-
Check Adobe Flash Player version on LinuxCheck the version file in the flash-plugin directory: cat /usr/lib/flash-plugin/version.properties or check the RPM/DEB package: rpm -q flash-plugin or dpkg -l | grep flashAffected if The version is 11.2.202.559 or earlier.
-
Check Adobe Air Desktop Runtime versionOn Windows, check the version in Add or Remove Programs or the file properties of AirRuntime.exe in the installation directory. On macOS, check /Applications/Adobe AIR Application Installer.app/Contents/Info.plist for CFBundleVersion.Affected if The version is 20.0.0.233 or earlier.
-
Check Adobe Air SDK versionLocate the air-sdk directory in your development environment and check the version.txt or SDKDescription.xml file, or run: adt -version if the AIR Developer Tool is available.Affected if The version is 20.0.0.233 or earlier.
If any installed Adobe Flash Player, Flash Player Desktop Runtime, Adobe Air Desktop Runtime, or Adobe Air SDK version falls at or below the thresholds listed (20.0.0.272, 18.0.0.326, 20.0.0.286, 11.2.202.559, or 20.0.0.233 depending on product and platform), the system is affected by CVE-2016-0984.
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.329, 20.0.0.306 or later (Windows/OS X) / 11.2.202.569 or later (Linux), and Adobe AIR to 20.0.0.260 or later. Since Flash Player is end-of-life, consider removing it entirely if no longer required.
Adobe Flash Player 20.0.0.306 (or 18.0.0.329/11.2.202.569 for Linux); Adobe AIR 20.0.0.260
- 1. Identify the exact Adobe Flash Player or AIR version currently installed on the system
- 2. For Windows/OS X Flash Player users: Upgrade to version 20.0.0.306 or later (or 18.0.0.329 for the 18.x branch)
- 3. For Linux Flash Player users: Upgrade to version 11.2.202.569 or later
- 4. For Adobe AIR Desktop Runtime users: Upgrade to version 20.0.0.260 or later
- 5. For Adobe AIR SDK users: Upgrade to version 20.0.0.260 or later
- 6. For Adobe AIR SDK & Compiler users: Upgrade to version 20.0.0.260 or later
- 7. Verify the installed version matches or exceeds the fixed release after upgrade
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-2016-0984 — 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-2016-0984 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