LiveActive security incident?Get immediate response
CVE Record

CVE-2016-0151: The Client-Server Run-time Subsystem (CSRSS) in Microsoft Windows 8.1, Windows Server 2012 Gold and R2, Win...

The Client-Server Run-time Subsystem (CSRSS) in Microsoft Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, and Windows 10 Gold and 1511 mismanages process tokens, which allows local users to gain privileges via a crafted application, aka "Windows CSRSS Security Feature Bypass Vulnerability."

HighCVSS 7.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2016-0151 is a Windows privilege-escalation issue in CSRSS token handling. An attacker who can run a crafted application locally could gain higher privileges. CISA lists it in KEV, so treat it as known exploited and prioritize remaining exposed legacy Windows systems.

Executive priority

High priority for legacy Windows environments because CISA KEV indicates known exploitation and successful abuse can elevate privileges. Internet exposure is not the main driver; business risk comes from post-compromise escalation on unpatched endpoints or servers.

Technical view

The CVE describes CSRSS mismanagement of process tokens on Windows 8.1, Windows Server 2012 Gold/R2, Windows RT 8.1, and Windows 10 Gold/1511. It is classified as CWE-269 with CVSS 7.8, local attack vector, low complexity, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on systems still running the Windows versions named in the CVE description and missing the MS16-048 security update. The bundle does not provide exact patch KBs, vulnerable build ranges beyond those names, or environmental prerequisites.

Exploitation context

CISA KEV status supports known exploitation. Exploit-DB is listed as a public exploit reference, but the source bundle does not establish current campaign activity, malware families, or remote exploitation. The flaw requires local execution of a crafted application.

Researcher notes

The supplied evidence supports a local privilege-escalation/security-feature-bypass analysis, not remote code execution. Affected products are taken from the CVE description. Patch specifics should be validated against MS16-048 because the bundle does not include KB-level details.

Mitigation direction

  • Apply Microsoft MS16-048 security updates where applicable.
  • Prioritize assets matching the Windows versions named in the CVE.
  • Consult Microsoft guidance for exact update applicability and replacement paths.
  • Restrict untrusted local code execution on exposed legacy systems.
  • Monitor privileged process creation on systems awaiting remediation.

Validation and detection

  • Inventory Windows 8.1, Windows Server 2012/R2, RT 8.1, and Windows 10 1507/1511 systems.
  • Verify MS16-048 or superseding Microsoft security updates are installed.
  • Confirm vulnerability scanner detection for CVE-2016-0151 is cleared.
  • Check CISA KEV tracking for required remediation deadlines.
  • Review endpoint telemetry for unusual local privilege escalation behavior.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-0151 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2016-0151Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-269 · source CWE mapping

Improper Privilege Management

Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.