dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-34719

HIGH · 7.8 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 →
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 Distributed File System (DFS) 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

Windows Distributed File System (DFS) contains an elevation of privilege vulnerability that could allow an authenticated attacker to gain higher-level system privileges. The specific technical details of the flaw (e.g., memory corruption, race condition) are not provided in the available description.

MitigationApply the relevant Microsoft security update for CVE-2022-34719 to the affected Windows systems running DFS, as patches address the privilege escalation mechanism.

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
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. Verify DFS component is installed
    On Windows Server, run 'Get-WindowsFeature -Name FS-DFS-Namespace,FS-DFS-Replication' in PowerShell. On Windows Client, check for DFS service by running 'Get-Service -Name Dfs*,Mrxdav' or check registry at HKLM\SYSTEM\CurrentControlSet\Services\Dfs*
    Affected if DFS Namespace or DFS Replication role is installed on Server, or DFS-related services exist on Client systems
  2. Confirm Windows version
    Run 'winver' or 'systeminfo | findstr /C:"OS Name" /C:"OS Version"' from command prompt, or 'Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion' in PowerShell
    Affected if Windows version matches any of the affected versions: Windows 10 (all versions, 1607, 1809, 20h2, 21h1, 21h2), Windows 11 (all versions), Windows 7 (all versions), Windows 8.1 (all versions), Windows Rt 8.1, Windows Server 2008/2008 R2, Windows Server 2012/2012 R2, Windows Server 2016 (all versions)
  3. Check if DFS service is running
    Run 'Get-Service -Name Dfs*' in PowerShell or 'sc query Dfs' in command prompt. Also check for 'DFS Namespace' or 'DFS Replication' services with 'Get-Service | Where-Object {$_.DisplayName -like "*DFS*"}'
    Affected if Any DFS-related service (DFS Namespace, DFS Replication) is in a Running or Stopped state (presence of the service indicates the vulnerable component is installed)
  4. Identify DFS namespaces or replicas configured
    Run 'dfsutil /Root:* /Enum' or 'dfscmd /view' to list configured DFS namespaces. In PowerShell, use 'Get-DfsnRoot | Select-Object Path,State' and 'Get-DfsrReplicatedFolder | Select-Object FolderName,State'
    Affected if Any DFS namespace or DFS replication folder is configured on the system

A system is affected if it runs any affected Windows version AND has the DFS component (DFS Namespace or DFS Replication role/service) installed, regardless of whether the service is currently running.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Microsoft security update for CVE-2022-34719 to the affected Windows systems running DFS, as patches address the privilege escalation mechanism.

Fix this in Windows 10 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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