CVE-2016-3351
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 · uneditedMicrosoft Internet Explorer 9 through 11 and Microsoft Edge allow remote attackers to obtain sensitive information via a crafted web site, aka "Microsoft Browser Information Disclosure Vulnerability."
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 confidenceMicrosoft Internet Explorer 9 through 11 and Microsoft Edge contain an information disclosure vulnerability where a remote attacker can obtain sensitive information by tricking a user into visiting a crafted malicious website. The vulnerability allows the attacker to access information that should be restricted.
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= 9= 10= 11all 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 Internet Explorer versionOpen Internet Explorer, click the gear icon > Settings > About Internet Explorer. Alternatively, check the registry key: HKLM\SOFTWARE\Microsoft\Internet Explorer at value 'Version'Affected if Version displayed is 9.x, 10.x, or 11.x
-
Identify Microsoft Edge versionOpen Microsoft Edge, click the three-dot menu > Settings > About Microsoft Edge. Alternatively, run PowerShell command: Get-AppxPackage Microsoft.MicrosoftEdge | Select-Object Name, VersionAffected if Any version number is returned (all Edge versions are affected)
-
Confirm browser is in active useCheck if Internet Explorer or Edge are listed as default browsers or have recent process history via Task ManagerAffected if Either browser shows recent use or is set as default
If either Internet Explorer version 9, 10, or 11 is installed, or Microsoft Edge of any version is present and actively used, the environment is affected by this information disclosure vulnerability.
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 the relevant Microsoft security update (MS16-104) to patch the vulnerability across affected browsers. Keep browsers updated and consider restricting access to untrusted websites until patches are applied.
Windows 10 with latest cumulative updates (Edge replaced IE on Windows 10)
- Enable Automatic Updates in Windows to receive Microsoft security patches automatically
- Run Windows Update and install all cumulative security updates for your Windows version
- Alternatively, manually download and install the specific security update for CVE-2016-3351 from the Microsoft Security Bulletin (MS16-104)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3351 — 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-3351 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