CVE-2016-0089
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 · uneditedHyper-V in Microsoft Windows 8.1, Windows Server 2012 Gold and R2, and Windows 10 allows guest OS users to obtain sensitive information from host OS memory via a crafted application, aka "Hyper-V 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 confidenceThis is an information disclosure vulnerability in Microsoft Hyper-V virtualization platform. A malicious guest OS user can craft an application to read sensitive memory contents from the host OS, bypassing isolation boundaries between guest and host. The vulnerability stems from improper memory access controls in the Hyper-V hypervisor.
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 versionsall versionsall versions= r2CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:C/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.
-
Verify Hyper-V role is installedRun 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' in PowerShell or check Programs and Features for Hyper-VAffected if Hyper-V is enabled and the Windows version is Windows 10, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2
-
Confirm Windows version is in affected rangeRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows versionAffected if Version is Windows 10 (any build), Windows 8.1 (any build), Windows Server 2012 (any build), or Windows Server 2012 R2 (any build)
-
Check if security update KB3140743 is installedRun 'Get-HotFix -Id KB3140743' in PowerShell or view installed updates in Control Panel > Programs > View installed updatesAffected if The update KB3140743 is NOT installed on the Hyper-V host
-
Verify memory access controls for guest VMsReview Hyper-V VM settings: right-click each VM > Settings > Memory - ensure 'Enable Memory Mirroring' is not configured in a way that exposes host memory to guests, or inspect via 'Get-VMMemory' PowerShell cmdletAffected if Guest VMs have been granted configurations that allow direct memory access or memory mirroring features are enabled without proper host protections
A system is affected if it runs Hyper-V on Windows 10, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2 AND the security update KB3140743 has not been applied.
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 Microsoft security patches for CVE-2016-0089 to all affected Windows hosts running Hyper-V (Windows 8.1, Windows Server 2012 R2, Windows 10). Ensure guest VMs are not granted excessive memory permissions and consider network segmentation to limit exposure.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0089 — 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-0089 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