dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2022-35759

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-31
Fix available
A fix is available. Upgrade to 6.3.9600.20520 / 10.0.10240.19387 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
Windows Local Security Authority (LSA) Denial of Service 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 10 1507Operating system
Affected:< 10.0.10240.19387
Windows 10 1607Operating system
Affected:< 10.0.14393.5291
Windows 10 1809Operating system
Affected:< 10.0.17763.3287
Windows 10 20h2Operating system
Affected:< 10.0.19042.1889
Windows 10 21h1Operating system
Affected:< 10.0.19043.1889
Windows 11 21h2Operating system
Affected:< 10.0.22000.856
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:< 6.3.9600.20520

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 6.3.9600.20520 / 10.0.10240.19387 / 10.0.14393.5291 or later
Fixed in 6.3.9600.2052010.0.10240.1938710.0.14393.5291
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

For Windows 10 1507: upgrade to 10.0.10240.19387 or later | Windows 10 1607: upgrade to 10.0.14393.5291 or later | Windows 10 1809: upgrade to 10.0.17763.3287 or later | Windows 10 20h2: upgrade to 10.0.19042.1889 or later | Windows 10 21h1: upgrade to 10.0.19043.1889 or later | Windows 11 21h2: upg

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Update by navigating to Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates for your Windows version
  4. Alternatively, manually download the specific security update from the Microsoft Catalog: https://catalog.update.microsoft.com/ (search for CVE-2022-35759)
  5. Restart the computer after the update is installed
  6. Verify the update was applied by checking Windows Update history
Caveat Security patches typically have minimal breaking changes; always test in non-production environments first. Note: Windows 7 reached end of support in 2020 and no longer receives security updates.

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-2022-35759 — 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-35759 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