Windows 10 1507Operating system · Microsoft

CVE-2022-22047

HIGH · 7.8 CVSS v3.1 Published 2022-07-12

Fix available

A fix is available. Upgrade to 10.0.10240.19360 / 10.0.14393.5246 or later.

See remediation →

96/100

Remediation priority · Urgent

In the wild Zero-click Patch available

Official description

NVD · unedited

Windows Client Server Run-time Subsystem (CSRSS) Elevation of Privilege Vulnerability

Technical summary

dbcve analysis · moderate confidence

This is a Windows Client Server Run-time Subsystem (CSRSS) Elevation of Privilege vulnerability. CSRSS is a critical Windows subsystem process responsible for Win32 console and GUI applications. The flaw allows a local attacker to escalate their privileges to a higher level, likely SYSTEM or kernel-level access, potentially leading to full system compromise.

MitigationApply the relevant Microsoft security update for CVE-2022-22047 via Windows Update or enterprise patch management systems. This vulnerability was addressed in Microsoft's July 2022 security updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Windows 10 1507Operating system

Affected:< 10.0.10240.19360

Windows 10 1607Operating system

Affected:< 10.0.14393.5246

Windows 10 1809Operating system

Affected:< 10.0.17763.3165

Windows 10 20h2Operating system

Affected:< 10.0.19042.1826

Windows 10 21h1Operating system

Affected:< 10.0.19043.1826

Windows 10 21h2Operating system

Affected:< 10.0.19044.1826

Windows 11 21h2Operating system

Affected:< 10.0.22000.795

Windows 7Operating system

Affected:all versions

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Determine Windows version and build number

Run 'winver' from command prompt or check System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'

Affected if The displayed build number falls below the safe threshold for your Windows version (see version-specific limits below)
Identify specific Windows 10 release

Run 'winver' and note the version (1507, 1607, 1809, 20h2, 21h1, or 21h2) or check the build number against known release builds

Affected if Build number is below 10.0.10240.19360 (1507), 10.0.14393.5246 (1607), 10.0.17763.3165 (1809), 10.0.19042.1826 (20h2), 10.0.19043.1826 (21h1), or 10.0.19044.1826 (21h2)
Check Windows 11 version

Run 'winver' or check System Information; Windows 11 21h2 shows as build 10.0.22000.xxx

Affected if Running Windows 11 21h2 with build below 10.0.22000.795
Confirm Windows 7 status

Run 'winver' or check System Properties; Windows 7 displays as version 6.1

Affected if Operating system is Windows 7 (any version, as all versions are affected)
Verify patch installation

Check Windows Update history for security update installed around July 2022 (CVE-2022-22047) or view installed updates via 'wmic qfe list'

Affected if No corresponding security update from July 2022 or later is installed

Your system is affected if it runs any Windows version with a build number lower than the threshold for that release, or if it is Windows 7, and the July 2022 security update for CVE-2022-22047 has not been applied.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 10.0.10240.19360 / 10.0.14393.5246 / 10.0.17763.3165 or later

Fixed in 10.0.10240.1936010.0.14393.524610.0.17763.3165

Vendor patch msrc.microsoft.com →

Interim mitigation

Apply the relevant Microsoft security update for CVE-2022-22047 via Windows Update or enterprise patch management systems. This vulnerability was addressed in Microsoft's July 2022 security updates.

Recommended fix High confidence

Upgrade to Windows 10 19044.1826+ (21h2), 19043.1826+ (21h1), 19042.1826+ (20h2), 17763.3165+ (1809), 14393.5246+ (1607), 10240.19360+ (1507), or Windows 11 22000.795+. For Windows 7, migrate to a supported OS (Windows 10/11).

Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
Identify the applicable Windows version from the affected list and note the required build number
For Windows 7 (all versions): Upgrade to a supported Windows version (Windows 10 or Windows 11) as Windows 7 is end-of-life with no security updates
For supported Windows versions: Apply the July 2022 Security Updates (or later) from Microsoft Update Catalog
Verify the update was installed successfully by checking Windows Update history or running 'winver' to confirm the build number matches or exceeds the fixed version
Restart the system as prompted to complete the installation
Confirm the vulnerability is resolved by verifying the CSRSS.exe version or using vulnerability scanning tools

Caveat Windows 7 reached end of support in January 2020 with no security updates; migration to Windows 10/11 required. Standard Windows update apply risks (plan for reboot, test compatibility).

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

11.0 hours of engineering $1,930

Get it fixed fast

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 locally

dbcve dependency scanner

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

Primary sources

msrc.microsoft.comPatch / commit
msrc.microsoft.comPatchVendor Advisory
www.cisa.govUS Government Resource
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22047 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-22047?

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.

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

At a glance

Exploited in the wildOn CISA’s known-exploited list · agencies must fix by 2022-08-02

A fix existsUpgrade to 10.0.10240.19360 / 10.0.14393.5246 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 17.1%

Affects: Windows 10 1507

Remediation

Being exploited — close it fast

Fix this in Windows 10 1507 11 hrs · Moderate

Typical engagement from $1,930

Get it fixed fast See the full breakdown ↓

This CVE is on CISA’s actively-exploited list, so the clock is real — a vetted specialist can deliver a reviewed fix for your staging environment quickly.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References