dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-34706

HIGH · 7.8 CVSS v3.1 Published 2022-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Local Security Authority (LSA) Elevation of Privilege 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 a Windows Local Security Authority (LSA) elevation of privilege vulnerability. The LSA is a critical Windows subsystem responsible for enforcing security policy, handling authentication, and managing user credentials. An authenticated attacker could potentially exploit this to elevate privileges from a low-privileged account to higher system or administrator levels.

MitigationApply the Microsoft security update for CVE-2022-34706, which is typically delivered via Windows Update or enterprise patch management systems. Prioritize patching domain controllers and systems with direct network 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
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 Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:all versions= 20h2

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

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

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 see the installed Windows version
    Affected if The version matches any of the affected versions listed: Windows 10 (all versions, 20h2, 21h1, 21h2, 1607, 1809), Windows 11 (all versions), Windows 7 (all versions), Windows 8.1 (all versions), Windows Rt 8.1 (all versions), Windows Server 2008 (all versions, R2), Windows Server 2012 (all versions,
  2. Verify LSA service is running
    Run 'Get-Service -Name LSASS' in PowerShell or check Services.msc for 'Local Security Authority Process' (lsass.exe)
    Affected if The LSASS service is running, which is the LSA process and the vulnerable component
  3. Check for installed security update
    Run 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"}' and look for KB5013663 (June 2022) or later security updates, or run 'wmic qfe list' to list installed hotfixes
    Affected if The security update for CVE-2022-34706 (June 2022 security update KB5013663 or later) is NOT installed
  4. Review security event logs for privilege escalation attempts
    Open Event Viewer, navigate to Windows Logs > Security, and look for Event ID 4672 (Special privileges assigned to new logon) or 4719 (System audit policy was changed) around the timeframe of concern
    Affected if Suspicious audit events indicate potential exploitation attempts, though this does not confirm vulnerability presence

The system is likely affected if it runs an affected Windows version and the CVE-2022-34706 security update (KB5013663 or later) is not installed.

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-34706, which is typically delivered via Windows Update or enterprise patch management systems. Prioritize patching domain controllers and systems with direct network exposure.

Recommended fix High confidence

August 2022 Windows Security Updates (or later)

  1. Open Windows Update by clicking the Start button and selecting Settings > Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. If prompted, restart your computer to complete the installation
  4. Verify the update was installed by checking Windows Update history for the August 2022 security updates (KB5016622, KB5016623, or subsequent relevant updates)
  5. For enterprise environments, deploy the update through your patch management system or WSUS
Caveat Ensure compatibility testing is performed on mission-critical systems before broad deployment; some legacy applications may experience issues after updates

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

Fix this in Windows 10 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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