.NET and Visual Studio Elevation of Privilege Vulnerability
🔗 CVE IDs covered (1)
📋 Description
What privileges could be gained by an attacker who successfully exploited the vulnerability? The attacker would gain the rights of the user that is running the affected application.
According to the CVSS metric, the attack vector is network (AV:N). How could an attacker exploit this vulnerability? An attacker could exploit this vulnerability by abusing the .NET diagnostics server to gain elevation of privileges.
According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability? Successful exploitation of this vulnerability requires an attacker to win a race condition and also to take additional actions prior to exploitation to prepare the target environment.
🎯 Affected products8
- .NET 6.0
- .NET 7.0
- Microsoft Visual Studio 2022 version 17.0
- Microsoft Visual Studio 2022 version 17.2
- Microsoft Visual Studio 2022 version 17.4
- Microsoft Visual Studio 2022 version 17.6
- PowerShell 7.2
- PowerShell 7.3
✅ Remediation
KB5028705 (Security Update) — fixed build 6.0.20 KB5028706 (Security Update) — fixed build 7.0.9 KBRelease Notes (Security Update) — fixed build 17.0.23 KBRelease Notes (Security Update) — fixed build 17.2.17 KBRelease Notes (Security Update) — fixed build 17.4.9 KBRelease Notes (Security Update) — fixed build 17.6.5 KBRelease Notes (Security Update) — fixed build 7.2.13 KBRelease Notes (Security Update) — fixed build 7.3.6
🔗 References (8)
- advisoryhttps://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-33127
- patchhttps://dotnet.microsoft.com/download/dotnet/6.0
- patchhttps://dotnet.microsoft.com/download/dotnet/7.0
- patchhttps://my.visualstudio.com/Downloads?q=Visual Studio 2022 version 17.0
- patchhttps://my.visualstudio.com/Downloads?q=Visual Studio 2022 version 17.2
- patchhttps://my.visualstudio.com/Downloads?q=Visual Studio 2022 version 17.4
- patchhttps://my.visualstudio.com/Downloads?q=Visual Studio 2022 version 17.6
- patchhttps://github.com/PowerShell/Announcements/issues/48