Vulnerability

CVE-2022-24521

High· 7.8KEVCVSS7.8EPSS7%

.rules3/5

Microsoft Windows CLFS Driver Privilege Escalation Vulnerability

Microsoft Windows Common Log File System (CLFS) Driver contains an unspecified vulnerability that allows for privilege escalation.

Threat signal

89/100

Severe

Severity

high

CVSS

7.8

EPSS

Active

KEV

CISA KEV — actively exploited

Ransomware: Known1501d overdue

AffectedMicrosoft — Windows

Added to KEV

2022-04-13

Federal patch due (BOD 22-01)

2022-05-04

Required action (CISA verbatim)

Apply updates per vendor instructions.

Vendor advisory + references

https://nvd.nist.gov/vuln/detail/CVE-2022-24521

CISA description: “Microsoft Windows Common Log File System (CLFS) Driver contains an unspecified vulnerability that allows for privilege escalation.”

CVSS

v3.1Open in FIRST calculator →

7.8/ 10HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack VectorLocalRequires local access — shell, console, or local app.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredLowStandard user privileges sufficient.
User InteractionNoneFully automated — no victim action needed.
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactHighTotal disclosure of sensitive data.
Integrity ImpactHighTotal compromise of integrity — full data modification possible.
Availability ImpactHighTotal loss of availability — full DoS possible.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

7.49%

probability of exploitation in next 30 days

p92

higher than 92% of all CVEs

3-day trend↑ 0pp

Mid-pack — moderate exploitation likelihood.

Vendor VEX

No VEX statements published for CVE-2022-24521. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCAct

Active exploitation with total impact on essential/support systems

exploitation: active
automatable: no
impact: total
mission: support

Lifecycle

2022-04-13Added to CISA KEVransomware: Known
2022-04-13Published
2022-05-04Federal patch due (BOD 22-01)
2026-06-12Last modified1 source

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.