dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2023-24903

HIGH · 8.1 CVSS v3.1 Published 2023-05-09
Fix available
A fix is available. Upgrade to 10.0.10240.19926 / 10.0.14393.5921 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Windows Secure Socket Tunneling Protocol (SSTP) 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-415

The same block of memory is freed twice, corrupting the allocator's bookkeeping in ways an attacker can shape toward code execution. It usually stems from tangled ownership of a pointer. The fix is clear, single ownership of each allocation and clearing pointers once they are freed.

General guidance for the double 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 10 1507Operating system
Affected:< 10.0.10240.19926
Windows 10 1607Operating system
Affected:< 10.0.14393.5921
Windows 10 1809Operating system
Affected:< 10.0.17763.4377
Windows 10 20h2Operating system
Affected:< 10.0.19042.2965
Windows 10 21h2Operating system
Affected:< 10.0.19044.2965
Windows 10 22h2Operating system
Affected:< 10.0.19045.2965
Windows 11 22h2Operating system
Affected:< 10.0.22000.1702
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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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.10240.19926 / 10.0.14393.5921 / 10.0.17763.4377 or later
Fixed in 10.0.10240.1992610.0.14393.592110.0.17763.4377
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Windows 10: Upgrade to build numbers >= 10.0.10240.19926 (1507), 10.0.14393.5921 (1607), 10.0.17763.4377 (1809), 10.0.19042.2965 (20h2), 10.0.19044.2965 (21h2), or 10.0.19045.2965 (22h2). Windows 11 22h2: Upgrade to build >= 10.0.22000.1702. Windows Server 2008/R2: Migrate to supported version (no p

  1. 1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
  2. 2. For Windows 10 1507: Upgrade to build 10.0.10240.19926 or later via Windows Update or Microsoft Update Catalog
  3. 3. For Windows 10 1607: Upgrade to build 10.0.14393.5921 or later via Windows Update or Microsoft Update Catalog
  4. 4. For Windows 10 1809: Upgrade to build 10.0.17763.4377 or later via Windows Update or Microsoft Update Catalog
  5. 5. For Windows 10 20h2: Upgrade to build 10.0.19042.2965 or later via Windows Update or Microsoft Update Catalog
  6. 6. For Windows 10 21h2: Upgrade to build 10.0.19044.2965 or later via Windows Update or Microsoft Update Catalog
  7. 7. For Windows 10 22h2: Upgrade to build 10.0.19045.2965 or later via Windows Update or Microsoft Update Catalog
  8. 8. For Windows 11 22h2: Upgrade to build 10.0.22000.1702 or later via Windows Update or Microsoft Update Catalog
Caveat Windows Server 2008/R2 has no security update available and requires migration to a supported Windows Server version

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,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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