CVE-2022-21871 | Microsoft Diagnostics Hub Standard Collector Runtime Elevation of Privilege Vulnerability

Microsoft Diagnostics Hub Standard Collector Runtime Elevation of Privilege Vulnerability

Published: 2022-01-11 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-21871 is rated Moderate Risk (46.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.31%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-21871

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-06 0.45% 0.31% -0.14%
2 2025-11-21 0.19% 0.45% +0.26%
3 2025-11-18 — 0.19% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-21871

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.0 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 5.9 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.2 2.0 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 3.9 10.0 [email protected]

Weakness enumeration for CVE-2022-21871

Affected software / configurations for CVE-2022-21871

Vendor Product Version Raw CPE
microsoft visual_studio_2017 >= 15.0, < 15.9.44 cpe:2.3:a:microsoft:visual_studio_2017:*:*:*:*:*:*:*:*
microsoft visual_studio_2019 >= 16.0, < 16.7.25 cpe:2.3:a:microsoft:visual_studio_2019:*:*:*:*:*:*:*:*
microsoft visual_studio_2019 >= 16.8, < 16.9.17 cpe:2.3:a:microsoft:visual_studio_2019:*:*:*:*:*:*:*:*
microsoft windows_10_1507 < 10.0.10240.19177 cpe:2.3:o:microsoft:windows_10_1507:*:*:*:*:*:*:x64:*
microsoft windows_10_1507 < 10.0.10240.19177 cpe:2.3:o:microsoft:windows_10_1507:*:*:*:*:*:*:x86:*
microsoft windows_10_1607 < 10.0.14393.4886 cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x64:*
microsoft windows_10_1607 < 10.0.14393.4886 cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x86:*
microsoft windows_10_1809 < 10.0.17763.2452 cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:*:*
microsoft windows_10_1909 < 10.0.18363.2037 cpe:2.3:o:microsoft:windows_10_1909:*:*:*:*:*:*:*:*
microsoft windows_10_20h2 < 10.0.19042.1466 cpe:2.3:o:microsoft:windows_10_20h2:*:*:*:*:*:*:*:*
microsoft windows_10_21h1 < 10.0.19043.1466 cpe:2.3:o:microsoft:windows_10_21h1:*:*:*:*:*:*:*:*
microsoft windows_10_21h2 < 10.0.19044.1466 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:*:*
microsoft windows_11_21h2 < 10.0.22000.434 cpe:2.3:o:microsoft:windows_11_21h2:*:*:*:*:*:*:*:*
microsoft windows_server 2022 cpe:2.3:o:microsoft:windows_server:2022:*:*:*:*:*:*:*
microsoft windows_server_2016 — cpe:2.3:o:microsoft:windows_server_2016:-:*:*:*:*:*:*:*
microsoft windows_server_2016 20h2 cpe:2.3:o:microsoft:windows_server_2016:20h2:*:*:*:*:*:*:*
microsoft windows_server_2019 — cpe:2.3:o:microsoft:windows_server_2019:-:*:*:*:*:*:*:*

References for CVE-2022-21871

cvelogic Threat Intelligence