CVE-2016-1100
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 · uneditedUnspecified vulnerability in Adobe Flash Player 21.0.0.213 and earlier, as used in the Adobe Flash libraries in Microsoft Internet Explorer 10 and 11 and Microsoft Edge, has unknown impact and attack vectors, a different vulnerability than other CVEs listed in MS16-064.
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 · moderate confidenceAn unspecified vulnerability in Adobe Flash Player 21.0.0.213 and earlier versions (as used in Microsoft IE10/11 and Edge) with unknown impact and attack vectors, but rated HIGH severity (CVSS 7.5), representing a different vulnerability than other issues addressed in MS16-064.
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<= 21.0.0.213all versions= 10= 11CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/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 in Internet ExplorerOpen Internet Explorer, navigate to the Adobe Flash Player test page at about:plugins (or check via Manage Add-ons > Show: All add-ons > Shockwave Flash Object), note the version number displayedAffected if The displayed version number is 21.0.0.213 or earlier (e.g., 21.0.0.182, 20.0.0.306, etc.)
-
Check if Flash is enabled in Internet ExplorerIn IE, go to Manage Add-ons > Show: All add-ons > Shockwave Flash Object. Verify the Status is EnabledAffected if Flash is Enabled AND the version is 21.0.0.213 or earlier
-
Check Adobe Flash Player version in EdgeIn Microsoft Edge, type edge://settings/manageFlash or navigate to edge://settings/ and look for Adobe Flash Player settings under Site permissionsAffected if Flash is allowed/enabled in Edge (Edge includes Flash by default in affected versions)
-
Verify Flash Player version via Windows registryOpen Registry Editor (regedit), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer (for 32-bit) or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Macromedia\FlashPlayer (for 64-bit), check the Version valueAffected if The Version value shows 21.0.0.213 or any version number lower than 21.0.0.213
Your environment is affected if Adobe Flash Player version 21.0.0.213 or earlier is installed and the Flash plugin is enabled in Internet Explorer 10/11 or Microsoft Edge.
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.
From vendor dataUpdate Adobe Flash Player to a version later than 21.0.0.213, or if Flash is no longer required, remove/disable the Flash plugin entirely as part of Flash's end-of-life decommissioning.
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1100 — 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-1100 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