Skip to content
Fencer Vulns
high 7.0

CVE-2022-29135 json

Windows Cluster Shared Volume (CSV) Elevation of Privilege Vulnerability

published 2022-05-10 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-33545

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

Summary

Windows Cluster Shared Volume (CSV) Elevation of Privilege 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

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 Vulns 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.