Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-23381: Visual Studio Remote Code Execution Vulnerability

42
This month
HIGH 7.8WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2023-23381 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.

Visual Studio Remote Code Execution Vulnerability

Why this priority

  • High severity
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.8 (High)
Attack vectorLocal
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.4% (top 62%)
CISA exploited listNo
WeaknessCWE-122
Published2023-02-14
Last modified2026-08-19
Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

microsoft visual studio 2017 UPGRADE
Affected: >= 15.0 and < 15.9.52
Fixed in: 15.9.52
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.52 (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.11.24
Fixed in: 16.11.24
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.11.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 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.19 · >= 17.2 and < 17.2.13 · >= 17.4 and < 17.4.5
Fixed in: 17.0.19, 17.2.13, 17.4.5
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.19 (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.
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-2023-23381?

visual studio 2017: upgrade to 15.9.52; visual studio 2019: upgrade to 16.11.24; visual studio 2022: upgrade to 17.0.19, 17.2.13, 17.4.5. Exact commands for each OS are on this page.

Is CVE-2023-23381 being exploited?

CVE-2023-23381 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-2023-23381 affect?

CVE-2023-23381 affects visual studio 2017, visual studio 2019, visual studio 2022. Severity is high (CVSS 7.8). Visual Studio Remote Code Execution Vulnerability

How urgent is CVE-2023-23381?

Priority 42/100. High severity; On your watchlist

Software pages

Visual Studio vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.