vciy

CVE-2024-21345

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Windows Kernel Elevation of Privilege Vulnerability

CVE-2024-213454 of 4 sources documented this
43

rank 43 = 18 + 22 + 1 + 2 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.20394  ·  without this subject the record ranks 25

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.8, from the CNA  ·  without this subject the record ranks 21

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-03-03  ·  without this subject the record ranks 42

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 41

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 43

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.02Mover the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$1.02M = $4.99M incident cost x 1 exposure x 0.20394 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.20394EPSSNOT IN KEVas of 2026-09-20
Severity8.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationpublic proof-of-conceptreceipt
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-06-15, 26 days at 0.20, as of 2026-07-11. arc-rules@v1

Foresight · where to check next

Microsoft WindowsMicrosoft WindowsMicrosoft WindowsMicrosoft Windows21345

This record is one instance of CWE-122, heap-based buffer overflow. The index holds 3216 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running Microsoft Windows Server 2022, 23H2…? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-122 Heap-based Buffer Overflowreceipt
Published consequencesCWE-122: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory); Integrity, Confidentiality, Availability, Access Control: Execute…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in10.0.25398.709receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 2 public repositories, 2024-04-26.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 2 public repositories2024-04-26receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA8.8 HIGHreceipt
Exploit probability0.20394 · top 3% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes42 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows Server 2022, 23H2 Edition (Server Core installation)receipt
Published rangesmicrosoft windows server 2022 23h2 < 10.0.25398.709receipt
Fixed in10.0.25398.709receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Local accessrequires low privilegesMicrosoft Windows Server 2022CWE-122 weaknessAdjacent componentsscope changeFull compromise (C/I/A)C:H / I:H / A:Hexploits CWE-122scope changedata compromise

What it is stated by the CNA

Windows Kernel Elevation of Privilege Vulnerability receipt

NVD's analysis a second authority

weakness
CWE-122
affected versions
microsoft windows server 2022 23h2 < 10.0.25398.709
also scored by
[email protected] 8.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

check it yourself msrc.microsoft.com receipt

Dated events

2025-03-17EPSS moved 0.00 to 0.292026-06-15EPSS moved 0.32 to 0.20

Movement the material steps

14 Feb 20240.00043
17 Mar 20250.29288 · crossed 0.10 · scoring model v2025.03.14
19 Mar 20250.17005
20 Mar 20250.29288
27 Mar 20250.17005
28 Mar 20250.29288
29 Mar 20250.17005
30 Mar 20250.29288
21 Apr 20250.41974
4 Jul 20250.25374
15 Jun 20260.20237 · scoring model v2026.06.15
11 Jul 20260.20394
Show all 39 observations
14 Feb 20240.00043
27 Feb 20240.00048
27 Apr 20240.00197
3 Nov 20240.02216
16 Nov 20240.00602
9 Dec 20240.01702
17 Dec 20240.00054
20 Dec 20240.00053
13 Jan 20250.00063
25 Jan 20250.00053
19 Feb 20250.00054
4 Mar 20250.00053
17 Mar 20250.29288
19 Mar 20250.17005
20 Mar 20250.29288
27 Mar 20250.17005
28 Mar 20250.29288
29 Mar 20250.17005
30 Mar 20250.29288
7 Apr 20250.28704
15 Apr 20250.37027
17 Apr 20250.38923
21 Apr 20250.41974
3 May 20250.38923
17 May 20250.39507
30 May 20250.38923
9 Jun 20250.36886
4 Jul 20250.25374
5 Oct 20250.27114
18 Nov 20250.28704
21 Nov 20250.27114
28 Dec 20250.25374
1 Jan 20260.20045
3 Mar 20260.26153
16 Mar 20260.31933
25 May 20260.32481
7 Jun 20260.31933
15 Jun 20260.20237
11 Jul 20260.20394

39 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.20394Published2024-02-13Public PoC2024-04-26Index as of2026-07-11

The record had been public for 2 years, 4 months when this index was last written.

Published 2024-02-13 receipt · Public PoC 2024-04-26 receipt · Index as of 2026-07-11 derived

The pattern, elsewhere

This record is one instance of CWE-122, heap-based buffer overflow. The index holds 3216 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2024-30051 · Microsoft Windows 10 Version 1809matches 8 of 9KEV listed · 2024receipt
CVE-2023-23376 · Microsoft Windows 10 Version 1507matches 8 of 9KEV listed · 2023receipt
CVE-2023-28252 · Microsoft Windows 10 Version 1809matches 8 of 9KEV listed · 2023receipt
CVE-2026-85880 · Microsoft Windows 10 Version 1607matches 8 of 9KEV listed · 2026receipt
CVE-2025-21333 · Microsoft Windows 10 Version 21H2matches 8 of 9KEV listed · 2025receipt
CVE-2025-21418 · Microsoft Windows 10 Version 1507matches 8 of 9KEV listed · 2025receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

3216 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

microsoft windows server 2022

Of the 6 records in this family that state one, this holds the highest EPSS percentile: 0.9731.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: computed, pro@dim2000

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2024-21345.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.