CVE-2016-0135
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 Secondary Logon Service in Microsoft Windows 10 Gold and 1511 allows local users to gain privileges via a crafted application, aka "Secondary Logon Elevation of Privilege 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 a local privilege escalation vulnerability in the Secondary Logon Service on Windows 10 (Gold and 1511 versions). An attacker with local access can craft a malicious application to elevate their privileges beyond their current user context, likely achieving SYSTEM or administrator-level access.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/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 Windows version and build numberOpen Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build numberAffected if The system is running Windows 10 Gold (build 10240) or Windows 10 version 1511 (build 10586)
-
Verify Secondary Logon Service is enabledOpen Services console (services.msc) or run 'sc query seclogon' to check if the Secondary Logon service is runningAffected if The Secondary Logon service (seclogon) is running or set to Automatic start
-
Confirm patch statusRun 'wmic qfe list' or check Windows Update history to see if security update KB3147458 is installedAffected if The system is missing security update KB3147458 (released April 2016) and is Windows 10 Gold or version 1511
-
Check user account privilegesRun 'whoami /priv' to list current user privileges, noting if SeCreateTokenPrivilege or other elevated privileges are presentAffected if Current user has limited privileges but the system remains unpatched, making privilege escalation possible
A user is affected if they are running Windows 10 Gold (1507) or version 1511 with the Secondary Logon service enabled and without security update KB3147458 installed.
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-0135. Additionally, restrict local user permissions and follow the principle of least privilege to limit the impact of potential exploitation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0135 — 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-0135 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