CVE-2016-7247
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 Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, and 1607, and Windows Server 2016 allow physically proximate attackers to bypass the Secure Boot protection mechanism via a crafted boot policy, aka "Secure Boot Component 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 vulnerability allows physically proximate attackers to bypass the Secure Boot protection mechanism in Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 by using a crafted boot policy. Secure Boot is designed to ensure only trusted operating systems load at startup, and this bypass could allow an attacker with physical access to load arbitrary operating systems or boot-level malware.
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= 1511= 1607all versionsall versionsall versions= r2all 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Secure Boot status in WindowsOpen PowerShell and run: 'Confirm-SecureBootUEFI'. If it returns True, Secure Boot is enabled. If it returns False or an error, it is disabled or not supported.Affected if The system returns True (Secure Boot is enabled) - this means the bypass vulnerability applies since the attacker would be bypassing an enabled Secure Boot protection
-
Confirm Windows version is affectedRun 'winver' or check System Properties to identify the exact Windows version and build number.Affected if Version is Windows 8.1, Windows 10 (any version including 1511 and 1607), Windows Server 2012, Windows Server 2012 R2, or Windows Server 2016
-
Check Secure Boot configuration via systeminfoRun 'systeminfo' from command prompt and look for the 'Secure Boot State' line in the output.Affected if Secure Boot State shows as 'Enabled' - indicating the protection is active and could be bypassed
-
Verify physical hardware presenceCheck if this is a physical machine rather than a virtual machine by running 'wmic computersystem get model' or inspecting BIOS/UEFI directly.Affected if System is physical hardware (not a VM) - the vulnerability requires physical access to the machine
The system is affected if Secure Boot is enabled on any Windows 8.1, Windows 10, Windows Server 2012/2012 R2, or Windows Server 2016 physical machine, as the vulnerability allows a physically proximate attacker to bypass this protection.
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 updates for this vulnerability when released, ensure physical security controls are in place for sensitive systems, and verify Secure Boot remains enabled and functioning properly after patching.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7247 — 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-7247 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