PatchTheCVECVE-2022-24767: GitHub: Git for Windows' uninstaller vulnerable to DLL hijacking when run under the SYSTEM user account.
51
This month
HIGH 7.8WATCHLISTUPGRADEUPGRADEUPGRADE
CVE-2022-24767 is a high-severity flaw (CVSS 7.8) affecting visual studio 2017, visual studio 2019, visual studio 2022. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
GitHub: Git for Windows' uninstaller vulnerable to DLL hijacking when run under the SYSTEM user account.
Why this priority
- High severity
- On your watchlist
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.8 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 1.5% (top 26%) |
| CISA exploited list | No |
| Weakness | CWE-427 |
| Published | 2022-04-12 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
microsoft visual studio 2017 UPGRADE
Affected: >= 15.0 and < 15.9.46
Fixed in: 15.9.46
Safe to downgrade to: a release before 15.0
1. Check installed version
apt-cache policy visual-studio-2017 || rpm -q visual-studio-2017 || visual-studio-2017 --version
2. UPGRADE to 15.9.46 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade visual-studio-2017
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade visual-studio-2017
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 15.0 (Debian / Ubuntu)
apt-cache madison visual-studio-2017
sudo apt install visual-studio-2017=<VERSION_BEFORE_15.0>
sudo apt-mark hold visual-studio-2017
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list visual-studio-2017
sudo dnf downgrade visual-studio-2017-<VERSION_BEFORE_15.0>
sudo dnf versionlock add visual-studio-2017
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
microsoft visual studio 2019 UPGRADE
Affected: >= 16.0 and < 16.7.27 · >= 16.8 and < 16.9.19 · >= 16.10 and < 16.11.12
Fixed in: 16.7.27, 16.9.19, 16.11.12
Safe to downgrade to: a release before 16.0
1. Check installed version
apt-cache policy visual-studio-2019 || rpm -q visual-studio-2019 || visual-studio-2019 --version
2. UPGRADE to 16.7.27 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade visual-studio-2019
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade visual-studio-2019
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 16.0 (Debian / Ubuntu)
apt-cache madison visual-studio-2019
sudo apt install visual-studio-2019=<VERSION_BEFORE_16.0>
sudo apt-mark hold visual-studio-2019
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list visual-studio-2019
sudo dnf downgrade visual-studio-2019-<VERSION_BEFORE_16.0>
sudo dnf versionlock add visual-studio-2019
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
microsoft visual studio 2022 UPGRADE
Affected: >= 17.0 and < 17.0.8 · >= 17.1.0 and < 17.1.4
Fixed in: 17.0.8, 17.1.4
Safe to downgrade to: a release before 17.0
1. Check installed version
apt-cache policy visual-studio-2022 || rpm -q visual-studio-2022 || visual-studio-2022 --version
2. UPGRADE to 17.0.8 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade visual-studio-2022
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade visual-studio-2022
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 17.0 (Debian / Ubuntu)
apt-cache madison visual-studio-2022
sudo apt install visual-studio-2022=<VERSION_BEFORE_17.0>
sudo apt-mark hold visual-studio-2022
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list visual-studio-2022
sudo dnf downgrade visual-studio-2022-<VERSION_BEFORE_17.0>
sudo dnf versionlock add visual-studio-2022
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
git for windows project git for windows UPGRADE
Affected: < 2.35.2
Fixed in: 2.35.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy git-for-windows || rpm -q git-for-windows || git-for-windows --version
2. UPGRADE to 2.35.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade git-for-windows
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade git-for-windows
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-24767?
visual studio 2017: upgrade to 15.9.46; visual studio 2019: upgrade to 16.7.27, 16.9.19, 16.11.12; visual studio 2022: upgrade to 17.0.8, 17.1.4. Exact commands for each OS are on this page.
Is CVE-2022-24767 being exploited?
CVE-2022-24767 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-24767 affect?
CVE-2022-24767 affects visual studio 2017, visual studio 2019, visual studio 2022. Severity is high (CVSS 7.8). GitHub: Git for Windows' uninstaller vulnerable to DLL hijacking when run under the SYSTEM user account.
How urgent is CVE-2022-24767?
Priority 51/100. High severity; On your watchlist
Software pages
GitHub vulnerabilities · Windows vulnerabilities · Git vulnerabilities · Visual Studio vulnerabilities
Related CVEs
- CVE-2026-47304 HIGH 8.1 DOWNGRADE UPGRADE Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security
- CVE-2022-24513 HIGH 7.8 UPGRADE UPGRADE Visual Studio Elevation of Privilege Vulnerability
- CVE-2023-23381 HIGH 7.8 UPGRADE UPGRADE Visual Studio Remote Code Execution Vulnerability
- CVE-2023-21815 HIGH 7.8 UPGRADE UPGRADE Visual Studio Remote Code Execution Vulnerability
- CVE-2023-21808 HIGH 7.8 DOWNGRADE UPGRADE .NET and Visual Studio Remote Code Execution Vulnerability