dbcve.org
Windows 11 21h2Operating system · Microsoft

CVE-2024-38259

HIGH · 8.8 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 10.0.20348.2700 / 10.0.22000.3197 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Management Console Remote Code Execution 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-416

Memory is used after it has been freed, so its contents — now potentially attacker-controlled — drive the program's behaviour. With careful heap grooming this becomes code execution. The fix requires disciplined ownership of memory and often a targeted rework of the object lifecycle.

General guidance for the use after free 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 11 21h2Operating system
Affected:< 10.0.22000.3197
Windows 11 22h2Operating system
Affected:< 10.0.22621.4169
Windows 11 23h2Operating system
Affected:< 10.0.22621.4169< 10.0.22631.4169
Windows 11 24h2Operating system
Affected:< 10.0.26100.1742
Windows Server 2022Operating system
Affected:< 10.0.20348.2700
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1128

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

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

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.20348.2700 / 10.0.22000.3197 / 10.0.22621.4169 or later
Fixed in 10.0.20348.270010.0.22000.319710.0.22621.4169
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Minimum fixed versions: Windows 11 21h2 (10.0.22000.3197), Windows 11 22h2/23h2 (10.0.22621.4169 or 10.0.22631.4169), Windows 11 24h2 (10.0.26100.1742), Windows Server 2022 (10.0.20348.2700), Windows Server 2022 23h2 (10.0.25398.1128)

  1. Check current Windows version by running 'winver' or 'systeminfo' in command prompt
  2. Open Windows Update by pressing Win + I, then navigate to Windows Update > Check for updates
  3. Install all available security updates, specifically looking for updates that address CVE-2024-38259
  4. If updates are managed via Group Policy or enterprise tools, deploy the relevant security patch from Microsoft Update Catalog or WSUS
  5. After installation, restart the computer to complete the patch deployment
  6. Verify the patch was installed successfully by checking Windows Update history for the KB corresponding to this CVE
Caveat Windows security updates typically have minimal breaking changes; ensure backups and test in non-production environments before broad deployment

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 $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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