CVE-2015-0006
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 · uneditedThe Network Location Awareness (NLA) service in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, and Windows Server 2012 Gold and R2 does not perform mutual authentication to determine a domain connection, which allows remote attackers to trigger an unintended permissive configuration by spoofing DNS and LDAP responses on a local network, aka "NLA Security Feature Bypass 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 confidenceThe Network Location Awareness (NLA) service in multiple Windows versions fails to perform mutual authentication when determining domain connections. Attackers on the local network can spoof DNS and LDAP responses to trick the system into an unintended permissive security configuration, bypassing the NLA security feature.
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 versionsall versionsall versionsall versions= r2all 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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Complete
- Availability
- None
AV:A/AC:L/Au:N/C:N/I:C/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 Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows version and build numberAffected if The version matches any of the affected products: Windows 7, 8, 8.1, Rt 8.1, Vista, Server 2003, Server 2008 (including R2), Server 2012 (including R2)
-
Verify NLA service is enabledRun 'sc query wlansvc' in command prompt or check Services.msc for the Network Location Awareness service (wlansvc)Affected if The Network Location Awareness service is running or set to Automatic start (vulnerable attack surface is present)
-
Check LDAP signing enforcementRun 'reg query HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters /v LDAPServerIntegrity' or use 'Get-ADObject' to query the LDAP signing policyAffected if The LDAPServerIntegrity value is not set to 2 (meaning LDAP signing is not required for domain connections)
-
Check channel binding token settingsRun 'reg query HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters /v LdapChannelBinding' to verify the channel binding configurationAffected if The LdapChannelBinding value is set to 0 or not present (meaning channel binding is not enforced)
A system is likely affected if it runs an affected Windows version, has NLA service enabled, and does not have LDAP signing and channel binding properly configured to enforce mutual authentication.
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 update for CVE-2015-0006 to all affected Windows systems. As a workaround, enforce LDAP signing and channel binding, and implement network segmentation to limit local network attack surface.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0006 — 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-2015-0006 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