dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 1 Nov 2022.
Windows 10 1507Operating system · Microsoft

CVE-2022-41033

HIGH · 7.8 CVSS v3.1 Published 2022-10-11
Fix available
A fix is available. Upgrade to 10.0.10240.19507 / 10.0.14393.5427 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click Patch available

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 COM+ Event System 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 COM+ Event System Service. An authenticated attacker could exploit this to gain higher privileges on the affected system. The specific technical details of the vulnerability (such as the flawed function or mechanism) are not provided in the available description.

MitigationApply the relevant Microsoft security update for CVE-2022-41033 to all affected Windows systems. Validate that the COM+ Event System Service is running with appropriate least-privilege configurations.

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 10 1507Operating system
Affected:< 10.0.10240.19507
Windows 10 1607Operating system
Affected:< 10.0.14393.5427
Windows 10 1809Operating system
Affected:< 10.0.17763.3532
Windows 10 20h2Operating system
Affected:< 10.0.19042.2130
Windows 10 21h1Operating system
Affected:< 10.0.19043.2130
Windows 10 21h2Operating system
Affected:< 10.0.19044.2130
Windows 11 21h2Operating system
Affected:< 10.0.22000.1098
Windows 11 22h2Operating system
Affected:< 10.0.22621.674

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. Retrieve Windows build version
    Open Command Prompt or PowerShell and run 'winver' to see the OS build number, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' for detailed version information
    Affected if The displayed build number falls below the threshold for your Windows version (10.0.10240.19507 for 1507, 10.0.14393.5427 for 1607, 10.0.17763.3532 for 1809, 10.0.19042.2130 for 20h2, 10.0.19043.2130 for 21h1, 10.0.19044.2130 for 21h2, 10.0.22000.1098 for Win11 21h2, 10.0.22621.674 for Win11 22h2)
  2. Confirm Windows edition and release
    Run 'winver' or check Settings > System > About to verify whether your Windows 10 edition is 1507, 1607, 1809, 20h2, 21h1, or 21h2, and for Windows 11 confirm whether it is 21h2 or 22h2
    Affected if You cannot determine the exact Windows release version needed for accurate version comparison
  3. Check COM+ Event System service status
    Open Services console (services.msc) or run 'Get-Service -Name "COMSysApp"' in PowerShell to verify the COM+ Event System service is present on the system
    Affected if The COM+ Event System service (COMSysApp) is not visible or listed on the system, as the vulnerability exists within this service component

Your system is affected if it runs a Windows 10 or Windows 11 version with a build number lower than the fixed build for your specific release, and the COM+ Event System service is present on the system.

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
Upgrade available Upgrade to 10.0.10240.19507 / 10.0.14393.5427 / 10.0.17763.3532 or later
Fixed in 10.0.10240.1950710.0.14393.542710.0.17763.3532
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the relevant Microsoft security update for CVE-2022-41033 to all affected Windows systems. Validate that the COM+ Event System Service is running with appropriate least-privilege configurations.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.19507 | Windows 10 1607: 10.0.14393.5427 | Windows 10 1809: 10.0.17763.3532 | Windows 10 20h2: 10.0.19042.2130 | Windows 10 21h1: 10.0.19043.2130 | Windows 10 21h2: 10.0.19044.2130 | Windows 11 21h2: 10.0.22000.1098 | Windows 11 22h2: 10.0.22621.674

  1. Open Settings on the Windows system
  2. Navigate to Windows Update > Check for updates
  3. Install all available security updates, which will include the fix for CVE-2022-41033
  4. Alternatively, manually download the specific security update for your Windows version from the Microsoft Update Catalog (search for KB5019961 or the October 2022 Security Updates)
  5. Restart the system after installing updates
  6. Verify the update was installed by checking the installed updates list for the October 2022 Security Update
Caveat Standard Windows security update; minimal risk of breaking changes

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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