CVE-2023-35391GHSA-J8RM-CM55-QQJ6BIT-ASPNET-CORE-2023-35391BIT-DOTNET-2023-35391BIT-DOTNET-SDK-2023-35391
ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.0.21, 7.0.10, 2.1.40, 17.2.18, 17.4.10, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Microsoft .NET 6.0
From 6.0.0 · fixed in 6.0.21
- Microsoft .NET 7.0
From 7.0.0 · fixed in 7.0.10
- Microsoft ASP.NET Core 2.1
From 2.0 · fixed in 2.1.40
- Microsoft Microsoft Visual Studio 2022 version 17.2
From 17.2.0 · fixed in 17.2.18
- Microsoft Microsoft Visual Studio 2022 version 17.4
From 17.4.0 · fixed in 17.4.10
- Microsoft Microsoft Visual Studio 2022 version 17.6
From 17.6.0 · fixed in 17.6.6
- Microsoft.AspNetCore.SignalR.StackExchangeRedisNuGet
From 7.0.0 · fixed in 7.0.10
- Microsoft.AspNetCore.SignalR.StackExchangeRedisNuGet
From 6.0.0 · fixed in 6.0.21
- Microsoft.AspNetCore.SignalR.RedisNuGet
fixed in 1.0.40