dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-30170

HIGH · 7.3 CVSS v3.1 Published 2022-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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 Credential Roaming Service 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 an Elevation of Privilege vulnerability in the Windows Credential Roaming Service. The vulnerability allows a low-privileged attacker to potentially gain higher privileges by exploiting how the credential roaming service handles credential storage and processing. Credential Roaming is a Windows feature that allows credentials to be stored and synchronized across systems in an Active Directory environment.

MitigationApply the relevant Microsoft security update for CVE-2022-30170 to all affected Windows systems. Prioritize patching domain controllers and systems with credential roaming enabled.

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

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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. Verify Windows version is affected
    Run 'winver' or 'systeminfo' or query the registry at 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' to identify the installed Windows version and build number
    Affected if The installed version matches any of the affected versions listed: Windows 10 (20h2, 21h1, 21h2, 1607, 1809), Windows 11, Windows 7, Windows 8.1, Windows Rt 8.1, Windows Server 2008/2008 R2, Windows Server 2012/2012 R2, or Windows Server 2016
  2. Confirm system is joined to Active Directory
    Run 'systeminfo' and check the 'Domain' field, or run 'whoami /groups' to see if the computer is domain-joined
    Affected if The system is joined to an Active Directory domain - credential roaming is an AD-specific feature and this vulnerability only applies in AD environments
  3. Determine if Credential Roaming is enabled
    Check the registry key 'HKLM\SYSTEM\CurrentControlSet\Services\CredentialRoaming' to see if the service exists and is configured, or check for the presence of credential roaming user profiles under 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList' that indicate roaming is in use
    Affected if Credential Roaming is enabled on the system - the vulnerability requires the credential roaming feature to be active for exploitation
  4. Check for the Credential Roaming service
    Run 'sc query CredentialRoaming' or check the services list via 'services.msc' to locate the Credential Roaming service
    Affected if The Credential Roaming service is present on the system - this indicates the feature may be available or has been installed

The system is likely affected if it runs an affected Windows version, is joined to an Active Directory domain, and has Credential Roaming enabled or the Credential Roaming service present.

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 relevant Microsoft security update for CVE-2022-30170 to all affected Windows systems. Prioritize patching domain controllers and systems with credential roaming enabled.

Recommended fix Moderate confidence

Apply the Microsoft security updates released in June 2022 or later for your specific Windows version

  1. Apply the Microsoft security update for CVE-2022-30170 from the Microsoft Security Response Center (msrc.microsoft.com)
  2. For Windows 10, 11, and Server versions, install the June 2022 or later monthly security update
  3. For Windows 7 and Windows Server 2008 R2, ensure Extended Security Updates (ESU) are enabled if applicable, then apply the security update
  4. Restart the affected systems after applying the update
  5. Verify the update is installed by checking Windows Update history or using the Get-HotFix PowerShell cmdlet
Caveat Standard Windows security update; no expected breaking changes for this elevation of privilege patch

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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