basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2022-22047
CVE-2022-22047 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Microsoft Windows vulnerability

Microsoft Windows CSRSS contains an unspecified privilege escalation vulnerability allowing attackers to gain SYSTEM-level access.

Verdict

Today item — known-exploited.

A privilege escalation flaw in the Windows Client/Server Runtime Subsystem enables local attackers to escalate from limited user context to SYSTEM privileges, facilitating post-compromise lateral movement and persistence.

CISA KEV Yes · 2022-07-123EPSS 0.18912 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-07-12).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.18912 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-426 Untrusted Search Path.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I gain initial access to a Windows system with limited user privileges through phishing, weak credentials, or another vector.
Business
An attacker establishes a foothold on an endpoint, creating risk of data exfiltration and malware deployment.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the CSRSS privilege escalation flaw to elevate my privileges to SYSTEM level on the compromised host.
Business
The attacker gains unrestricted control of the endpoint, enabling installation of rootkits, credential theft, and lateral movement across the network.
3

Lateral reach — past segmentation narrative 3

Attacker
With SYSTEM privileges, I establish persistence mechanisms and move laterally to critical systems and sensitive data repositories.
Business
The organization faces potential compromise of domain controllers, file servers, and databases, leading to widespread data breach and operational disruption.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 9 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.