CVE-2022-24513: Visual Studio Elevation of Privilege Vulnerability

This month

HIGH 7.8WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2022-24513 is a high-severity flaw (CVSS 7.8) affecting visual studio 2017, visual studio 2019, visual studio 2019. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Visual Studio Elevation of Privilege Vulnerability

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	Low
User interaction	None
EPSS exploit chance	0.8% (top 45%)
CISA exploited list	No
Published	2022-04-15
Last modified	2026-10-23

Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Last updated 2026-10-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-04-15 19:15 UTCPublished CVE record published
2026-10-23 17:33 UTCUpdated Record last modified

microsoft visual studio 2017 UPGRADE

Affected: >= 15.9 and < 15.9.49

Fixed in: 15.9.49

Safe to downgrade to: a release before 15.9

1. Check installed version

apt-cache policy visual-studio-2017 || rpm -q visual-studio-2017 || visual-studio-2017 --version

2. UPGRADE to 15.9.49 (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.9 (Debian / Ubuntu)

apt-cache madison visual-studio-2017 sudo apt install visual-studio-2017=<VERSION_BEFORE_15.9> 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.9> 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: >= 8.10 and < 8.10.24

Fixed in: 8.10.24

Safe to downgrade to: a release before 8.10

1. Check installed version

apt-cache policy visual-studio-2019 || rpm -q visual-studio-2019 || visual-studio-2019 --version

2. UPGRADE to 8.10.24 (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 8.10 (Debian / Ubuntu)

apt-cache madison visual-studio-2019 sudo apt install visual-studio-2019=<VERSION_BEFORE_8.10> 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_8.10> 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 2019 UPGRADE

Affected: >= 16.7 and < 16.7.27 · >= 16.9 and < 16.9.23 · >= 16.11 and < 16.11.16

Fixed in: 16.7.27, 16.9.23, 16.11.16

Safe to downgrade to: a release before 16.7

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.7 (Debian / Ubuntu)

apt-cache madison visual-studio-2019 sudo apt install visual-studio-2019=<VERSION_BEFORE_16.7> 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.7> 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.3

Fixed in: 17.0.3

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.3 (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.

microsoft visual studio 2022 UPGRADE

Affected: >= 17.0 and < 17.0.12 · >= 17.1 and < 17.1.7

Fixed in: 17.0.12, 17.1.7

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.12 (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.

Exact fixes by distribution

Fedora 46 · retext · FIXED · 8.1.0-1.fc46 · FEDORA-2026-0602a84203 · source

sudo dnf upgrade --advisory=FEDORA-2026-0602a84203

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.

Quick answers

How do I fix CVE-2022-24513?

visual studio 2017: upgrade to 15.9.49; visual studio 2019: upgrade to 8.10.24; visual studio 2019: upgrade to 16.7.27, 16.9.23, 16.11.16. Exact commands for each OS are on this page.

Is CVE-2022-24513 being exploited?

CVE-2022-24513 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-24513 affect?

CVE-2022-24513 affects visual studio 2017, visual studio 2019, visual studio 2019. Severity is high (CVSS 7.8). Visual Studio Elevation of Privilege Vulnerability

How urgent is CVE-2022-24513?

Priority 46/100. High severity; On your watchlist

Software pages

Visual Studio vulnerabilities

References

← Back to latest CVEs