CVE-2022-41077
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 · uneditedWindows Fax Compose Form 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 confidenceThis is a local Elevation of Privilege (EoP) vulnerability in the Windows Fax Compose Form component. The vulnerability allows a low-privileged user to potentially gain higher privileges by exploiting the fax compose functionality, likely through improper input validation or privilege handling within the form.
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 dataall versions= 20h2= 21h1= 21h2= 22h2= 1607= 1809all versionsall versionsall versionsall versionsall versions= r2all versions= r2all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the installed Windows version and build numberAffected if The version matches any of the affected versions: Windows 10 (20h2, 21h1, 21h2, 22h2, 1607, 1809), Windows 11 (all), Windows 7 (all), Windows 8.1 (all), Windows Rt 8.1 (all), Windows Server 2008/2008 R2, Windows Server 2012/2012 R2, or Windows Server 2016 (all)
-
Check if Fax service is presentRun 'Get-Service -Name Fax' in PowerShell or check Services.msc for the Fax serviceAffected if The Fax service exists on the system (faxsvc or similar service name is found)
-
Verify Fax and Scan Windows feature is installedRun 'Get-WindowsOptionalFeature -Online -FeatureName FaxServices' or check Control Panel > Programs > Turn Windows features on or off for Fax and ScanAffected if The Fax and Scan Windows feature is enabled or installed on the system
-
Check fax-related DLL versionsLocate fax DLLs such as fxscompose.dll or fxssvc.exe in the Windows\System32 directory and check their file properties for version infoAffected if The fax compose component DLLs (fxscompose.dll) are present on the system, indicating the vulnerable component exists
-
Verify if Fax service is runningRun 'Get-Service -Name Fax | Select-Object Status' or check if fxssvc.exe process is active in Task ManagerAffected if The Fax service is currently running (status shows 'Running'), making the attack surface active
The system is potentially affected if it runs an affected Windows version AND has the Fax service or Fax and Scan feature present, regardless of whether the service is currently running, since the vulnerable code exists in the fax compose form component.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the Microsoft security update (KB5019966 or subsequent patches) to all affected Windows systems to address the vulnerability in the Fax Compose Form component.
- Apply the Microsoft security update for CVE-2022-41077 via Windows Update or download the update from the Microsoft Update Catalog
- For systems without automatic updates enabled, manually check for and install the latest Windows security updates
- Verify the update KB329046 is installed after applying the patch
- Restart the system as required to complete the update installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41077 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41077 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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