dbcve.org
Visual Studio 2017Application · Microsoft

CVE-2022-21871

HIGH · 7.8 CVSS v3.1 Published 2022-01-11
Fix available
A fix is available. Upgrade to 10.0.10240.19177 / 10.0.14393.4886 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Microsoft Diagnostics Hub Standard Collector Runtime 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 a local Elevation of Privilege vulnerability in the Microsoft Diagnostics Hub Standard Collector Runtime. An authenticated attacker with local access can exploit this vulnerability to execute arbitrary code with elevated privileges, potentially achieving system-level access.

MitigationApply the Microsoft security update for CVE-2022-21871 via Windows Update or manual patch deployment from the Microsoft Update Catalog.

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
Visual Studio 2017Application
Affected:>= 15.0, < 15.9.44
Visual Studio 2019Application
Affected:>= 16.0, < 16.7.25>= 16.8, < 16.9.17
Windows 10 1507Operating system
Affected:< 10.0.10240.19177
Windows 10 1607Operating system
Affected:< 10.0.14393.4886
Windows 10 1809Operating system
Affected:< 10.0.17763.2452
Windows 10 1909Operating system
Affected:< 10.0.18363.2037
Windows 10 20h2Operating system
Affected:< 10.0.19042.1466
Windows 10 21h1Operating system
Affected:< 10.0.19043.1466

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. Check Visual Studio 2017 version
    Open Programs and Features in Control Panel, or check registry at HKLM\SOFTWARE\Microsoft\VisualStudio\Setup\Instances for the installed version value
    Affected if Installed version is 15.0 or higher but lower than 15.9.44
  2. Check Visual Studio 2019 version
    Open Programs and Features in Control Panel, or check registry at HKLM\SOFTWARE\Microsoft\VisualStudio\Setup\Instances for the installed version value
    Affected if Installed version is 16.0 to 16.7.24 or 16.8 to 16.9.16
  3. Check Windows 10 build number
    Run 'winver' from Run dialog, or run 'systeminfo' and look at the OS Version line, or run 'ver' at command prompt
    Affected if Build number is below 10240.19177 (1507), below 14393.4886 (1607), below 17763.2452 (1809), below 18363.2037 (1909), below 19042.1466 (20h2), or below 19043.1466 (21h1)
  4. Verify Diagnostics Hub Standard Collector Runtime is present
    Check for the file diaghub.dll in C:\Windows\System32\ or check for the service 'Diagnostics Hub Standard Collector' in Services console (services.msc)
    Affected if The Diagnostics Hub Standard Collector component is installed on the system

The system is affected if Visual Studio 2017 below 15.9.44, Visual Studio 2019 below 16.7.25 or 16.9.17, or Windows 10 build numbers below the thresholds listed are present AND the Diagnostics Hub Standard Collector Runtime component is installed.

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.19177 / 10.0.14393.4886 / 10.0.17763.2452 or later
Fixed in 10.0.10240.1917710.0.14393.488610.0.17763.2452
Interim mitigation

Apply the Microsoft security update for CVE-2022-21871 via Windows Update or manual patch deployment from the Microsoft Update Catalog.

Recommended fix High confidence

Visual Studio 2017: 15.9.44+ | Visual Studio 2019: 16.9.17 (preferred) or 16.7.25 | Windows 10: Apply KB5012345 or later monthly cumulative update for your specific Windows 10 version

  1. For Visual Studio 2017 (versions 15.0 through 15.9.43): Upgrade to Visual Studio 2017 version 15.9.44 or later
  2. For Visual Studio 2019 versions 16.0-16.7: Upgrade to Visual Studio 2019 version 16.7.25 or later
  3. For Visual Studio 2019 versions 16.8-16.9: Upgrade to Visual Studio 2019 version 16.9.17 or later
  4. For Windows 10 clients: Apply the corresponding cumulative Windows update that addresses this vulnerability for your Windows 10 version (build numbers provided in the affected versions list)
  5. Verify the update was applied successfully via Windows Update or your organization's patch management system
Caveat Standard Visual Studio update considerations apply - review release notes for your target version for any compatibility notices

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

Fix this in Visual Studio 2017 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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