dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-23297

MEDIUM · 5.5 CVSS v3.1 Published 2022-03-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Windows NT Lan Manager Datagram Receiver 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 · moderate confidence

This is an information disclosure vulnerability in the Windows NT Lan Manager Datagram Receiver Driver (also known as the NLM or Msnldp.sys driver), which handles connectionless datagram communications in Windows networking stacks. The vulnerability allows a local attacker to potentially read sensitive information from kernel memory due to improper bounds checking or memory handling in the driver.

MitigationApply the Microsoft security update for CVE-2022-23297, which patches the vulnerable Windows kernel driver. On legacy systems where patches are unavailable, consider network segmentation and restricting local access privileges to minimize exposure.

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 10Operating system
Affected:all versions= 20h2= 21h1= 21h2= 1607= 1809= 1909
Windows 11Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions
Windows ServerOperating system
Affected:= 20h2= 2022
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating 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
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. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the installed Windows version and build number
    Affected if The system is running any version of Windows 10 (20h2, 21h1, 21h2, 1607, 1809, 1909), Windows 11, Windows 7, Windows 8.1, Windows Rt 8.1, Windows Server 2008, Windows Server 2012, Windows Server 20h2, or Windows Server 2022
  2. Locate the Msnldp.sys driver
    Search for the driver file using 'dir /s C:\Windows\System32\drivers\Msnldp.sys' or 'Get-ChildItem -Path C:\ -Recurse -Filter Msnldp.sys -ErrorAction SilentlyContinue'
    Affected if The Msnldp.sys driver file exists on the system (typically in C:\Windows\System32\drivers\)
  3. Check if the driver is loaded
    Run 'driverquery /v | findstr Msnldp' or check the kernel module list via 'systeminfo' or 'msinfo32' under 'Kernel Modules'
    Affected if The Msnldp.sys driver is listed as loaded or running in the system driver list
  4. Verify security update installation
    Run 'wmic qfe list' or 'Get-HotFix | Where-Object {$_.Description -like "Security Update"}' and search for the CVE-2022-23297 related patch (typically a February 2022 or later security update)
    Affected if No security update addressing CVE-2022-23297 is installed on the system

If the system runs an affected Windows version, contains the Msnldp.sys driver, and is missing the corresponding security patch, the environment is vulnerable to CVE-2022-23297.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security update for CVE-2022-23297, which patches the vulnerable Windows kernel driver. On legacy systems where patches are unavailable, consider network segmentation and restricting local access privileges to minimize exposure.

Recommended fix High confidence
  1. Open Windows Update by pressing the Windows key and typing 'Windows Update'
  2. Click 'Check for updates' to connect to Microsoft Update
  3. Install all available security updates, specifically looking for the CVE-2022-23297 security update
  4. Restart the computer if prompted to complete the installation
  5. Verify the update was installed by viewing update history

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

Fix this in Windows 10 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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