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

Microsoft Windows vulnerability

Microsoft Windows Common Log File System (CLFS) driver vulnerability allows privilege escalation through improper input validation and buffer operations.

Verdict

Today item — known-exploited.

A privilege escalation flaw in the Windows CLFS driver enables local attackers to gain elevated system access. The vulnerability has been exploited in active attacks and involves improper input handling and memory corruption.

CISA KEV Yes · 2022-09-143EPSS 0.28483 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
13 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-09-14).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.28483 — 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-20 Improper Input Validation, CWE-787 Out-of-bounds Write — weakness family: Memory safety.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 craft malicious input to the CLFS driver to trigger improper validation.
Business
An attacker gains a foothold on the system through local access.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the buffer operation flaw to corrupt memory and escalate privileges.
Business
The attacker obtains system-level permissions, bypassing access controls.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code with elevated privileges to install persistence mechanisms.
Business
The organization loses control of affected systems and faces data compromise risk.
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)
  • Public PoC available (VulnCheck)
  • 13 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • 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.