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

Microsoft Windows vulnerability

Microsoft Windows NTFS logs sensitive information that can be disclosed through physical access, potentially exposing heap memory contents.

Verdict

Today item — known-exploited.

An attacker with physical access to a Windows system can extract sensitive data from NTFS log files, leading to information disclosure. This vulnerability is being actively exploited in the wild.

CISA KEV Yes · 2025-03-113EPSS 0.01831 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
5 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 2025-03-11).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.01831 — 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-532 CWE-532.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 physical access to a Windows device and examine NTFS log files stored on disk.
Business
Sensitive information resident in heap memory is exposed through inadequately protected logging mechanisms.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I extract portions of heap memory contents by parsing log data without requiring authentication.
Business
Confidential data such as credentials, encryption keys, or user information may be recovered from memory dumps in logs.
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)
  • 5 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.