Skip to content
Fencer Intel
medium 5.5

CVE-2022-29102 json

Windows Failover Cluster Information Disclosure Vulnerability

published 4y ago modified 4mo ago also EUVD-2022-33513

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

Windows Failover Cluster Information Disclosure Vulnerability

Patch / fix

  • Microsoft Windows Server 2019 10.0.17763.2928
  • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.2928
  • Microsoft Windows Server 2022 10.0.20348.707
  • Microsoft Windows Server version 20H2 10.0.19042.1706
  • Microsoft Windows Server 2016 10.0.14393.5125
  • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.5125
  • Microsoft Windows Server 2012 6.2.9200.23714
  • Microsoft Windows Server 2012 (Server Core installation) 6.2.9200.23714
  • Microsoft Windows Server 2012 R2 6.3.9600.20371
  • Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.20371

Is CVE-2022-29102 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.9 AV:L/AC:L/Au:N/C:C/I:N/A:N

Affected products

  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2019 (Server Core installation)
  • Microsoft Windows Server 2022
  • Microsoft Windows Server version 20H2
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2016 (Server Core installation)
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 (Server Core installation)
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012 R2 (Server Core installation)

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.