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

Microsoft Windows vulnerability

Microsoft Windows Graphic Component vulnerability allowing privilege escalation via integer overflow. Actively exploited in the wild.

Verdict

Today item — known-exploited.

Integer overflow in Windows graphics processing enables local privilege escalation. Active exploitation observed. Requires local access but grants elevated system permissions, posing significant risk to Windows deployments.

CISA KEV Yes · 2023-02-143EPSS 0.05563 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
4 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 2023-02-14).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.05563 — 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-190 Integer Overflow — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-190 · Integer OverflowMemory safety
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 a malicious input to the graphics component that triggers an integer overflow condition.
Business
An attacker gains local code execution with elevated privileges, bypassing access controls.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the overflow to write to protected memory regions and escalate my process privileges.
Business
System integrity is compromised as the attacker operates with kernel-level or SYSTEM account permissions.
3

Lateral reach — past segmentation narrative 3

Attacker
I maintain persistence or move laterally across the network using elevated access.
Business
Organizational security perimeter is breached; lateral movement enables compromise of additional systems and data exfiltration.
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)
  • 4 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.