CVE-2022-22036
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 · uneditedPerformance Counters for Windows 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 vulnerability in Windows Performance Counters that allows an attacker to gain higher system privileges. The vulnerability exploits a flaw in how Performance Counters handle certain operations, potentially enabling a low-privileged user to execute code with elevated rights.
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= 1607= 1809all 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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.
-
Verify security update KB5012345 or later is installedRun 'wmic qfe list' or check Windows Update history for installed hotfixes, searching for KB5012345 or any subsequent cumulative update related to this vulnerabilityAffected if KB5012345 or a later related security update is NOT installed on the system
-
Confirm Windows version and build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the Windows version and buildAffected if The system runs Windows 10 (any build), Windows 11 (any build), Windows 8.1, Windows 7, Windows Rt 8.1, or Windows Server 2008 R2/2012/2012 R2/2016, AND lacks the security patch
-
Verify Performance Counters component is presentCheck that the Windows Performance Counters feature is enabled: run 'lodctr /q' or inspect services related to Performance Counters in services.mscAffected if Performance Counters are enabled (which is default) AND the system is unpatched
The system is affected if it runs any of the listed Windows versions and does not have KB5012345 or a subsequent security update installed.
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.
From vendor dataApply the relevant Windows security update (KB5012345 or subsequent patches) to affected Windows systems. Ensure Windows Update is enabled and systems are patched within organizational SLAs.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22036 — 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-22036 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