CVE-2016-0150
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 · uneditedHTTP.sys in Microsoft Windows 10 Gold and 1511 allows remote attackers to cause a denial of service (system hang) via crafted HTTP 2.0 requests, aka "HTTP.sys Denial of Service 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 confidenceHTTP.sys in Microsoft Windows 10 Gold and 1511 contains a denial of service vulnerability where specially crafted HTTP 2.0 requests can cause the system to hang. The vulnerability is remotely exploitable via network requests to the HTTP service.
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= 1511CVSS 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
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Windows 10 version and build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows 10 build. Affected versions are Windows 10 Gold (build 10240) and Windows 10 version 1511 (build 10586).Affected if The system runs Windows 10 with build 10240 or 10586 (version 1511).
-
Verify HTTP service is runningRun 'sc query http' or check the HTTP Driver service status via Services.msc. Also run 'netsh http show servicestate' to see if HTTP.sys is active.Affected if The HTTP service (HTTP.sys driver) is running and handling HTTP requests.
-
Confirm HTTP 2.0 protocol is enabledCheck registry key 'HKLM\SYSTEM\CurrentControlSet\Services\HTTP\Parameters' for EnableHttp2Tls and EnableHttp2Cleartext values, or inspect IIS site bindings for HTTP/2 protocol support.Affected if HTTP 2.0 is explicitly enabled on the system or IIS site bindings.
-
Assess network exposure of HTTP servicesRun 'netsh http show urlacl' and 'netstat -ano | findstr :80 :443' to determine if HTTP services are bound to accessible network interfaces.Affected if The HTTP service is bound to routable IP addresses and exposed to untrusted networks.
A system is affected if it runs Windows 10 build 10240 or 10586, has HTTP.sys active with HTTP 2.0 enabled, and the HTTP service is network-accessible to untrusted sources.
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 CVE-2016-0150 to affected Windows 10 systems. Until patched, consider restricting exposure of HTTP services to untrusted networks or implementing rate limiting on perimeter devices.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0150 — 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-0150 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