dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-24992

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 10.0.10240.20947 / 10.0.14393.7876 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer over-read in Windows NTFS allows an unauthorized attacker to disclose information locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer over-read vulnerability exists in the Windows NTFS file system driver that allows a local attacker to read memory beyond allocated buffer boundaries. This can enable disclosure of sensitive information from kernel memory through specially crafted file system operations.

MitigationApply the Microsoft security update for CVE-2025-24992 to affected Windows systems. Enforce least-privilege user accounts to limit local attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20947
Windows 10 1607Operating system
Affected:< 10.0.14393.7876
Windows 10 21h2Operating system
Affected:< 10.0.19044.5608
Windows 10 22h2Operating system
Affected:< 10.0.19045.5608
Windows 11 22h2Operating system
Affected:< 10.0.22621.5039
Windows 11 23h2Operating system
Affected:< 10.0.22631.5039
Windows 11 24h2Operating system
Affected:< 10.0.26100.3403
Windows Server 2008Operating system
Affected:all versions= r2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to retrieve the full build number
    Affected if The build number falls below the fixed version for your Windows release (e.g., below 10.0.19045.5608 for Windows 10 22h2, below 10.0.22621.5039 for Windows 11 22h2)
  2. Verify NTFS driver version
    Run 'driverquery /v | findstr ntfs.sys' or check file properties of C:\Windows\System32\ntfs.sys to obtain the driver version
    Affected if The ntfs.sys version is lower than the build-specific version thresholds listed in the CVE advisory
  3. Confirm Windows edition and build manually
    Run 'winver' to get exact Windows edition (e.g., 1507, 1607, 21h2, 22h2) and cross-reference with the fixed build numbers for that specific edition
    Affected if Your Windows edition build is less than the corresponding patched build for that specific release channel

A system is affected if its Windows build number is lower than the patched version for its specific release (or any Windows Server 2008/R2 version, which has no patch).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20947 / 10.0.14393.7876 / 10.0.19044.5608 or later
Fixed in 10.0.10240.2094710.0.14393.787610.0.19044.5608
Interim mitigation

Apply the Microsoft security update for CVE-2025-24992 to affected Windows systems. Enforce least-privilege user accounts to limit local attack surface.

Recommended fix High confidence

Upgrade to the minimum fixed build version for your Windows release (e.g., Windows 10 22h2 build 19045.5608, Windows 11 23h2 build 22631.5039). For Windows Server 2008/R2, migrate to a supported Windows Server version as it is end-of-life with no patch.

  1. 1. Identify the Windows version currently installed by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows 10 or 11 version family applies to your system from the affected versions list
  3. 3. For Windows 10 1507 systems: Upgrade to Windows 10 version 10.0.10240.20947 or later
  4. 4. For Windows 10 1607 systems: Upgrade to Windows 10 version 10.0.14393.7876 or later
  5. 5. For Windows 10 21h2 systems: Upgrade to Windows 10 version 10.0.19044.5608 or later
  6. 6. For Windows 10 22h2 systems: Upgrade to Windows 10 version 10.0.19045.5608 or later
  7. 7. For Windows 11 22h2 systems: Upgrade to Windows 11 version 10.0.22621.5039 or later
  8. 8. For Windows 11 23h2 systems: Upgrade to Windows 11 version 10.0.22631.5039 or later
Caveat Upgrades within the same Windows version should not have breaking changes; however, Windows Server 2008/R2 is end-of-life and requires a full OS migration to a supported version.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24992 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data