dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-24069

MEDIUM · 5.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.10240.21034 / 10.0.14393.8148 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
Out-of-bounds read in Windows Storage Management Provider allows an authorized 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 · moderate confidence

Out-of-bounds read vulnerability in Windows Storage Management Provider enables a locally authenticated attacker to read memory beyond intended boundaries, potentially disclosing sensitive information. The vulnerability stems from improper bounds checking in the storage management component.

MitigationApply Microsoft security updates for Windows via Windows Update or enterprise patch management systems once released. Prioritize patching systems with local attacker access.

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.21034
Windows 10 1607Operating system
Affected:< 10.0.14393.8148
Windows 10 1809Operating system
Affected:< 10.0.17763.7434
Windows 10 21h2Operating system
Affected:< 10.0.19044.5965
Windows 10 22h2Operating system
Affected:< 10.0.19045.5965
Windows 11 22h2Operating system
Affected:< 10.0.22621.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Determine Windows version number
    Run 'winver' from command prompt or check HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion in Registry for the Build Number value
    Affected if The installed build number falls below the threshold for your specific Windows release (10.0.10240 for 1507, 10.0.14393 for 1607, 10.0.17763 for 1809, 10.0.19044 for 21h2, 10.0.19045 for 22h2, 10.0.22621 for 11 22h2, 10.0.22631 for 11 23h2, 10.0.26100 for 11 24h2)
  2. Confirm Windows release branch
    Run 'winver' to identify if the system is Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, or 24h2
    Affected if The system matches any of the affected release branches listed in the CVE
  3. Check Storage Management Provider service
    Run 'Get-Service -Name Storsvc' in PowerShell or check Services list for 'Windows Storage Management Service'
    Affected if The StorSvc service exists and is present on the system (this is the vulnerable component)
  4. Verify local authentication context
    Review user account privileges on the system using 'whoami /all' or Local Users and Groups management
    Affected if An attacker with local authenticated access to the system can trigger the vulnerable code path in Storage Management Provider

A system is affected if it runs any of the listed Windows 10 or Windows 11 versions with a build number lower than the fixed version AND has the Storage Management Provider component present.

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.21034 / 10.0.14393.8148 / 10.0.17763.7434 or later
Fixed in 10.0.10240.2103410.0.14393.814810.0.17763.7434
Interim mitigation

Apply Microsoft security updates for Windows via Windows Update or enterprise patch management systems once released. Prioritize patching systems with local attacker access.

Recommended fix High confidence

Minimum fixed versions: Windows 10 1507: 10.0.10240.21034 | Windows 10 1607: 10.0.14393.8148 | Windows 10 1809: 10.0.17763.7434 | Windows 10 21h2: 10.0.19044.5965 | Windows 10 22h2: 10.0.19045.5965 | Windows 11 22h2: 10.0.22621.5472 | Windows 11 23h2: 10.0.22631.5472 | Windows 11 24h2: 10.0.26100.42

  1. Check the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify which Windows 10 or Windows 11 version and build is installed
  3. Apply the appropriate Windows security update from Microsoft Update Catalog or Windows Update
  4. Restart the system after installing the update
  5. Verify the update was installed successfully by checking Windows Update history
Caveat Standard Windows update - no breaking changes expected for this informational disclosure vulnerability patch

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24069 — 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-24069 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