How to Fix CVE-2022-41073: Out-of-bounds Write in Windows 10 Version 1809

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2022-21999: Path Traversal in Microsoft Windows — Path Traversal in Microsoft Windows
• How to Fix CVE-2022-21919: Improper Link Resolution Before File Access in Microsoft Windows — Improper Link Resolution Before File Access in Microsoft Windows
• How to Fix CVE-2022-41091: Incorrect Authorization in Windows 10 Version 1809 , Incorrect Authorization in Windows 10 Version 1809
• How to Fix CVE-2022-24521: Out-of-Bounds Write in Microsoft Windows , Out-of-Bounds Write in Microsoft Windows
• How to Fix CVE-2022-41082: Deserialization of Untrusted Data , Deserialization of Untrusted Data

*By Sai Kiran Pandrala*

Patch immediately. CISA's Known Exploited Vulnerabilities catalog lists this CVE, which means active exploitation has been confirmed. CISA KEV entry added 2022-11-08, federal due date 2022-12-09.

What is CVE-2022-41073?

CVE-2022-41073 is a out-of-bounds write in Windows 10 Version 1809 from Microsoft. Windows Print Spooler Elevation of Privilege Vulnerability

Why this CVE matters

This CVE sits on CISA's Known Exploited Vulnerabilities catalog, which only happens after active exploitation is observed in the wild. The out-of-bounds write class of flaw gives attackers a reliable foothold against vulnerable instances of Windows 10 Version 1809. If your deployment matches the affected versions, treat any window of unpatched exposure as compromise-likely and review logs accordingly.

Am I affected?

Run the version check that matches your platform. If the installed build sits inside the affected range from the table above, the fix applies to you.

# Linux package check
dpkg -s windows10version1809 2>/dev/null | grep -i version    # Debian / Ubuntu
rpm -q windows10version1809 2>/dev/null                       # RHEL / Rocky

# Windows version check
Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Windows 10 Version 1809' } | Select-Object Name,Version

How to fix CVE-2022-41073

Apply the patched build the vendor names in the advisory. The commands below are starting points keyed to common platforms - adapt the package name and target version to your environment.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade windows10version1809
# verify the package version matches the fixed release in the advisory
dpkg -s windows10version1809 | grep -i version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --refresh windows10version1809 -y
rpm -q windows10version1809

Container image

# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41073
# Pull the patched base image and rebuild
docker pull <your-registry>/windows10version1809:<patched-tag>
docker build -t <your-app>:patched .
docker stop <your-app> && docker rm <your-app>
docker run -d --name <your-app> <your-app>:patched

Windows (PowerShell, run as administrator)

# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41073
# Make sure Windows Update is current. For monthly rollups this is the safest path.
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Import-Module PSWindowsUpdate
Get-WindowsUpdate -KBArticleID <KB-from-advisory>
Install-WindowsUpdate -KBArticleID <KB-from-advisory> -AcceptAll -AutoReboot

# Confirm the KB landed
Get-HotFix | Where-Object { $_.HotFixID -eq 'KB<id>' }

# Or, for an MSU file downloaded from the Microsoft Update Catalog:
wusa.exe C:\Patches\windows10.0-kb<id>-x64.msu /quiet /norestart
shutdown /r /t 60

PowerShell detect/upgrade/verify/log (Windows)

# CVE-2022-41073 remediation runner — adapt the version checks to your environment.
$log = "C:\Logs\CVE-2022-41073-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'Windows 10 Version 1809' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2022-41073-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    # Example MSI:  Start-Process msiexec.exe -ArgumentList '/i C:\Patches\Windows 10 Version 1809-patched.msi /qn /norestart' -Wait
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Windows 10 Version 1809' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged - check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

Bash detect/upgrade/verify/log (Linux)

#!/usr/bin/env bash
# CVE-2022-41073 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2022-41073-fix.log; }

log "Detect: current windows10version1809 version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' windows10version1809 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' windows10version1809 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current"

log "Backup: snapshotting config"
backup="/var/backups/cve-2022-41073-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/windows10version1809 ] && cp -a /etc/windows10version1809 "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade windows10version1809
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y windows10version1809
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y windows10version1809
fi

log "Verify: re-reading windows10version1809 version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' windows10version1809)
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' windows10version1809)
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: windows10version1809 upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

After the upgrade, restart any service that loads the patched binary so the new code is actually running.

If you can't patch immediately

Patching is the only durable fix. These mitigations cut exposure while the change window is scheduled, they do not remove the vulnerability.

Windows: disable the vulnerable feature via registry

# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41073
# Replace <Component> / <Setting> with the exact key from the vendor advisory.
# Always export the key first so you can roll back.
reg export "HKLM\SOFTWARE\Vendor\windows 10 version 1809" "C:\Backup\preFix-CVE-2022-41073.reg" /y
Set-ItemProperty -Path "HKLM:\SOFTWARE\Vendor\windows 10 version 1809" -Name "Disable<Setting>" -Value 1 -Type DWord
Restart-Service -Name "<service-name>" -Force

How to verify the fix worked

After applying the patched build, confirm the version string matches the fixed release named in the Microsoft advisory.

dpkg -s windows10version1809 | grep -i version       # Debian / Ubuntu
rpm -q windows10version1809                          # RHEL / Rocky

Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2022-41073. For internet-facing deployments that were unpatched during the disclosure window, review logs for the affected endpoints over the full exposure period and rotate any credentials the vulnerable process could touch.

Frequently asked questions

Is CVE-2022-41073 being exploited in the wild?

Yes. CISA added CVE-2022-41073 to the Known Exploited Vulnerabilities catalog, which means active exploitation has been confirmed.

Will a firewall rule or WAF signature fully mitigate CVE-2022-41073?

No. Network-layer filters slow opportunistic scanners and block a subset of payloads, but a focused attacker who knows the bug will work around them. The vendor patch is the only durable fix.

Do I need to assume compromise if the affected service was internet-facing and unpatched?

For a CVE that CISA confirms is under active exploitation, yes. Review logs for the affected endpoints over the entire exposure window, rotate credentials the vulnerable process could read, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

• Official vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41073
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2022-41073
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• CISA KEV record: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-41073
• Additional reference: http://packetstormsecurity.com/files/174528/Microsoft-Windows-Privilege-Escalation.html
• Additional reference: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-41073

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*