CVE-2022-34690
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 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 confidenceAn Elevation of Privilege (EoP) vulnerability exists in the Windows Fax Service that allows an authenticated attacker to gain higher-level system privileges. The vulnerability stems from improper privilege handling within the fax service 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 dataall versions= 20h2= 21h1= 1607= 1809all versionsall versionsall versionsall versionsall versions= r2all versions= r2all versions= 20h2CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Check Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build numberAffected if The version matches any of the affected products: Windows 10 (all versions, including 20h2, 21h1, 1607, 1809), Windows 11 (all versions), Windows 7 (all versions), Windows 8.1 (all versions), Windows Rt 8.1 (all versions), Windows Server 2008 (all versions, including R2), Windows Server 2012 (all ve
-
Verify Windows Fax Service is installedRun 'sc query Fax' or check Services.msc for the 'Windows Fax' or 'Fax' service entryAffected if The Fax service is present on the system (service name is 'Fax')
-
Check if Windows Fax Service is runningRun 'sc query state= all' and look for SERVICE_RUNNING status for the Fax service, or check via 'services.msc'Affected if The Fax service is currently running (SERVICE_RUNNING state)
-
Check Fax service executable pathRun 'sc qc Fax' to query the service configuration and verify the binary path points to the fax service componentAffected if The service configuration exists and points to a fax-related executable (typically %SystemRoot%\System32\faxsvc.dll or similar)
-
Verify authentication contextReview system logs (Security event logs) for any recent authenticated sessions or service account usage related to the Fax serviceAffected if The system has authenticated users or the Fax service runs under a privileged account context
The system is potentially affected if it runs any of the affected Windows versions AND has the Windows Fax Service installed, regardless of running state, as the vulnerability exists in the service component itself.
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 for CVE-2022-34690 to patch the Windows Fax Service vulnerability. Prioritize systems running the fax service component.
Apply Microsoft security update KB5015861 or subsequent relevant security patch for your Windows version
- Check Windows Update or Microsoft Update Catalog for the latest security updates
- Locate the specific security update for CVE-2022-34690 (search by CVE number)
- Download and install the applicable security update for your Windows version
- Restart the system as prompted to complete the patch installation
- Verify the update was installed successfully via Windows Update history
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34690 — 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-34690 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