dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-41058

HIGH · 7.5 CVSS v3.1 Published 2022-11-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Network Address Translation (NAT) 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 · moderate confidence

This is a Denial of Service (DoS) vulnerability in Windows Network Address Translation (NAT) functionality. The vulnerability allows an attacker to cause the NAT component to become unresponsive or crash, disrupting network connectivity for affected systems.

MitigationApply Microsoft security updates for CVE-2022-41058 when released. Until then, network segmentation and firewall rules may help limit exposure to remote attackers targeting the NAT component.

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= 22h2= 1607= 1809
Windows 11Operating system
Affected:all versions= 22h2
Windows 7Operating system
Affected:= sp1
Windows 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
Windows Server 2019Operating 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 check System Properties to determine the exact Windows version and build number (e.g., 20h2, 21h1, 21h2, 22h2 for Windows 10; 22h2 for Windows 11; or check Windows Server versions 2008, 2008 R2, 2012, 2012 R2, 2016, 2019). Compare your version against the affected list: Windows 10 versions 20h2, 21h1, 21h2, 22h2, 1607, 1809; Windows 11 version 22h2; Windows 7 SP1; Windows 8.1; Windows Server 2008/2008 R2, 2012/2012 R2, 2016, 2019.
    Affected if Running any version listed in the affected products (Windows 10 specific versions, Windows 11 22h2, Windows 7 SP1, Windows 8.1, or Windows Server 2008 through 2019)
  2. Verify NAT feature is enabled
    On the system, open Windows Features (optionalfeatures.exe) and check if 'Windows Network Address Translation' (NAT) is enabled, or via PowerShell run 'Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*NAT*"}' to list NAT-related features.
    Affected if The NAT component is installed and enabled on the system
  3. Confirm NAT is actively in use
    Check for active NAT configuration by running 'netsh routing ip nat show global' or examining routing tables and RAS connections that may be using NAT. Also check if the system is acting as a gateway or router.
    Affected if The system is actively using NAT functionality (configured as a NAT gateway or routing NAT traffic)

A system is affected if it runs an affected Windows version AND has the NAT component enabled and actively in use, making it vulnerable to DoS via the NAT component becoming unresponsive.

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 Microsoft security updates for CVE-2022-41058 when released. Until then, network segmentation and firewall rules may help limit exposure to remote attackers targeting the NAT component.

Recommended fix Moderate confidence

Apply Microsoft November 2022 security updates (KB5020030 or subsequent relevant security rollup for your Windows version); for end-of-life systems, upgrade to Windows 10/11 or Windows Server 2016/2019/2022

  1. Open Windows Update on the affected system
  2. Check for and install the November 2022 security updates from Microsoft
  3. If running end-of-life versions (Windows 7 SP1, Windows 8.1, Windows Server 2008 R2, Windows Server 2012 R2), migrate to a supported Windows version as these versions no longer receive security updates
  4. After applying the update, restart the system to ensure the NAT component is updated
  5. Verify the update was installed successfully by checking Windows Update history
Caveat Standard patch risks apply - test in non-production environment before broad deployment; end-of-life versions require operating system upgrade rather than patching

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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