CVE-2016-0110
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 10 through 11 and Microsoft Edge allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Microsoft Browser Memory Corruption 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 · moderate confidenceA memory corruption vulnerability in Microsoft Internet Explorer 10-11 and Microsoft Edge allows remote attackers to execute arbitrary code or cause denial of service via a crafted malicious website. The vulnerability stems from improper memory handling in the browser's rendering engine, which can be exploited to achieve code execution in the context of the current user.
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 dataall 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 if Internet Explorer 10 or 11 is installedOpen Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v VersionAffected if The returned version value equals 10.0.x or 11.0.x (where x is any build number)
-
Check if Microsoft Edge is installedOpen Command Prompt and run: reg query "HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\App Paths\msedge.exe" /ve or check C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe existenceAffected if Microsoft Edge executable is found on the system (all versions are affected)
-
Confirm browser is actually usedCheck if Internet Explorer or Edge executables (iexplore.exe or msedge.exe) exist in typical paths such as C:\Program Files\Internet Explorer\iexplore.exe or C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exeAffected if Either iexplore.exe or msedge.exe executables are present on the system
-
Determine if security patches are appliedOpen Command Prompt and run: wmic qfe list | findstr /i "MS16-023" (or check Windows Update history for security update KB3141099)Affected if The specific MS16-023 security update or KB3141099 is NOT listed as installed
If Internet Explorer version 10 or 11 OR Microsoft Edge of any version is installed AND MS16-023 (KB3141099) is not installed, the system is vulnerable to CVE-2016-0110.
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 dataApply the Microsoft security updates for this vulnerability (MS16-023 or subsequent related bulletins), and ensure browsers are automatically updated. Users should avoid visiting untrusted websites until patches are applied.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0110 — 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-0110 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