dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-38122

MEDIUM · 5.5 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 10.0.10240.20751 / 10.0.14393.7259 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

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
Microsoft Local Security Authority (LSA) Server Information Disclosure Vulnerability

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
How this class of weakness works · CWE-908

Memory or a resource is used before it has been initialised, so its contents are whatever happened to be there — sometimes leaking earlier data, sometimes values an attacker can influence. Behaviour becomes unpredictable and occasionally exploitable. Remediation is initialising every resource before use and ensuring initialisation happens on all code paths.

General guidance for the use of uninitialized resource class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.20751
Windows 10 1607Operating system
Affected:< 10.0.14393.7259
Windows 10 1809Operating system
Affected:< 10.0.17763.6189
Windows 10 21h2Operating system
Affected:< 10.0.19044.4780
Windows 10 22h2Operating system
Affected:< 10.0.19045.4780
Windows 11 21h2Operating system
Affected:< 10.0.22000.3147
Windows 11 22h2Operating system
Affected:< 10.0.22621.4037
Windows 11 23h2Operating system
Affected:< 10.0.22631.4037

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

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.20751 / 10.0.14393.7259 / 10.0.17763.6189 or later
Fixed in 10.0.10240.2075110.0.14393.725910.0.17763.6189
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Upgrade to the appropriate fixed Windows build for your version: 10.0.10240.20751 (Win10 1507), 10.0.14393.7259 (Win10 1607), 10.0.17763.6189 (Win10 1809), 10.0.19044.4780 (Win10 21h2), 10.0.19045.4780 (Win10 22h2), 10.0.22000.3147 (Win11 21h2), 10.0.22621.4037 (Win11 22h2), or 10.0.22631.4037 (Win1

  1. Identify the Windows version and build number by running 'winver' or 'systeminfo'
  2. Determine which affected version bracket your system falls into (Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 21h2, 22h2, 23h2)
  3. Open Windows Update by pressing Windows Key + I, then navigating to Windows Update
  4. Click 'Check for updates' and install all available security updates
  5. Alternatively, manually download and install the specific KB update for CVE-2024-38122 from the Microsoft Update Catalog: https://catalog.update.microsoft.com/
  6. After installation, restart the system to apply the LSA security update
  7. Verify the version has been updated to one of the fixed builds: 10.0.10240.20751 (1507), 10.0.14393.7259 (1607), 10.0.17763.6189 (1809), 10.0.19044.4780 (21h2), 10.0.19045.4780 (22h2), 10.0.22000.3147 (21h2), 10.0.22621.4037 (22h2), or 10.0.22631.4037 (23h2)
Caveat Standard Windows cumulative update with no expected breaking changes; as with any security update, test in a staging environment if possible

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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