dbcve.org
Windows 10Operating system · Microsoft

CVE-2023-24857

MEDIUM · 6.5 CVSS v3.1 Published 2023-03-14
Fix available
A fix is available. Upgrade to 10.0.10240.19805 / 10.0.14393.5786 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 PostScript and PCL6 Class Printer Driver 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

A detailed technical summary for this CVE is being prepared.

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 10Operating system
Affected:< 10.0.10240.19805
Windows 10 1607Operating system
Affected:< 10.0.14393.5786
Windows 10 1809Operating system
Affected:< 10.0.17763.4131
Windows 10 20h2Operating system
Affected:< 10.0.19042.2728
Windows 10 21h2Operating system
Affected:< 10.0.19044.2728
Windows 10 22h2Operating system
Affected:< 10.0.19045.2728
Windows 11 21h2Operating system
Affected:< 10.0.22000.1696
Windows 11 22h2Operating system
Affected:< 10.0.22000.1413

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

CVSS:3.1/AV:N/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.19805 / 10.0.14393.5786 / 10.0.17763.4131 or later
Fixed in 10.0.10240.1980510.0.14393.578610.0.17763.4131
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Windows 10/11 with security update containing CVE-2023-24857 patch (minimum build numbers listed above per version)

  1. Check current Windows version by running `winver` or `systeminfo` in Command Prompt
  2. Identify which Windows 10 or Windows 11 version/build is currently installed
  3. Apply the appropriate Windows Update or download the cumulative update that includes the security fix for CVE-2023-24857
  4. For Windows 10 versions: Ensure update to build 10.0.10240.19805 or higher (original), 10.0.14393.5786 or higher (1607), 10.0.17763.4131 or higher (1809), 10.0.19042.2728 or higher (20h2), 10.0.19044.2728 or higher (21h2), or 10.0.19045.2728 or higher (22h2)
  5. For Windows 11 versions: Ensure update to build 10.0.22000.1696 or higher (21h2) or 10.0.22000.1413 or higher (22h2)
  6. Verify successful installation by re-checking the Windows build version
Caveat Standard Windows update risks apply - ensure backups and compatibility testing for critical systems before 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 $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-2023-24857 — 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-24857 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