Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

CVSS 3.1 6.2 MEDIUMEUVD CVSS 3.1 6.2 CVSS 3.1 · [email protected] · Secondary 6.2 MEDIUMCVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS_V3 Publisher rating HIGHFixed by Microsoft.AspNetCore.SignalR.StackExchangeRedis 7.0.10Fixed by Microsoft.AspNetCore.SignalR.StackExchangeRedis 6.0.21Fixed by Microsoft.AspNetCore.SignalR.Redis 1.0.40KEV status unknown

cve-program · CVE-2023-35391

Published

ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

Read the publisher's advisory

euvd · EUVD-2023-2314

Published

ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

Read the publisher's advisory

nvd · CVE-2023-35391

Published

ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

Read the publisher's advisory

osv · GHSA-j8rm-cm55-qqj6

Published

# Microsoft Security Advisory CVE-2023-35391: .NET Information Disclosure Vulnerability ## <a name="executive-summary"></a>Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET core 2.1, .NET 6.0 and, .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in ASP.NET Core 2.1, .NET 6.0 and, .NET 7.0 applications using SignalR when redis backplane use might result in information disclosure. ## Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/267 ### <a name="mitigation-factors"></a>Mitigation factors Microsoft has not identified any mitigating factors for this vulnerability. ## <a name="affected-software"></a>Affected software * Any .NET 7.0 application running on .NET 7.0.9 or earlier. * Any .NET 6.0 application running on .NET 6.0.20 or earlier. If your application uses the following package versions, ensure you update to the latest version of .NET. ### <a name=".NET 7"></a>.NET 7 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.AspNetCore.SignalR.StackExchangeRedis](https://www.nuget.org/packages/Microsoft.AspNetCore.SignalR.StackExchangeRedis) | >= 7.0.0, <= 7.0.9 | 7.0.10 ### <a name=".NET 6"></a>.NET 6 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.AspNetCore.SignalR.StackExchangeRedis](https://www.nuget.org/packages/Microsoft.AspNetCore.SignalR.StackExchangeRedis) | >= 6.0.0, <= 6.0.20 | 6.0.21 ### <a name="ASP.NET Core 2.1"></a>ASP.NET Core 2.1 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.AspNetCore.SignalR.Redis](https://www.nuget.org/packages/Microsoft.AspNetCore.SignalR.Redis) | < 1.0.40 | 1.0.40 ## Advisory FAQ ### <a name="how-affected"></a>How do I know if I am affected? If you have a runtime or SDK with a version listed, or an affected package listed in [affected software](#affected-software), you're exposed to the vulnerability. ### <a name="how-fix"></a>How do I fix the issue? * To fix the issue please install the latest version of .NET 6.0 or .NET 7.0. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs. * If you are using one of the affected packages, please update to the patched version listed above. * If you have .NET 6.0 or greater installed, you can list the versions you have installed by running the `dotnet --info` command. You will see output like the following; ``` .NET Core SDK (reflecting any global.json): Version: 6.0.300 Commit: 8473146e7d Runtime Environment: OS Name: Windows OS Version: 10.0.18363 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\6.0.300\ Host (useful for support): Version: 6.0.5 Commit: 8473146e7d .NET Core SDKs installed: 6.0.300 [C:\Program Files\dotnet\sdk] .NET Core runtimes installed: Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] To install additional .NET Core runtimes or SDKs: https://aka.ms/dotnet-download ``` * If you're using .NET 7.0, you should download and install Runtime 7.0.10 or SDK 7.0.110 (for Visual Studio 2022 v17.4) from https://dotnet.microsoft.com/download/dotnet-core/7.0. * If you're using .NET 6.0, you should download and install Runtime 6.0.21 or SDK 6.0.316 (for Visual Studio 2022 v17.2) from https://dotnet.microsoft.com/download/dotnet-core/6.0. .NET 6.0 and and .NET 7.0 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates. Once you have installed the updated runtime or SDK, restart your apps for the update to take effect. Additionally, if you've deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. ## Other Information ### Reporting Security Issues If you have found a potential security issue in .NET 6.0 or .NET 7.0, please email details to [email protected]. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at <https://aka.ms/corebounty>. ### Support You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue. ### Disclaimer The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. ### External Links [CVE-2023-35391]( https://www.cve.org/CVERecord?id=CVE-2023-35391) ### Revisions V1.0 (August 08, 2023): Advisory published. _Version 1.0_ _Last Updated 2023-08-08_

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

CVE-2023-35391

This is a saved version of the risk data. The advisory details have their own history. Latest risk data.

No CISA KEV listing is included in this saved record. Exploitation may still have occurred.

FIRST EPSS: 1.90 % · percentile 79.87 % · scored 9 Nov 2026. This score is more than two days old.

Saved 09 Nov 2026 21:04:24 UTC · View this risk record (JSON)

cve-program · CVE-2023-35391

Published

ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

Source published
8 Aug 2023 18:52:30 UTC
Source modified
10 Aug 2026 15:11:59 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C

euvd · EUVD-2023-2314

Published

ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 8, 2023, 6:52:30 PM

dateUpdated: Aug 10, 2026, 3:11:59 PM

4 related source bulletins · separate from aliases

NCSC-2024-0246: Kwetsbaarheden verholpen in Siemens producten

CVE-2023-28319 · CVE-2023-28484 · CVE-2023-29331 · CVE-2023-29469 · CVE-2023-32032 · CVE-2023-33126 · CVE-2023-33127 · CVE-2023-33128 · CVE-2023-33135 · CVE-2023-33170 · CVE-2023-35390 · CVE-2023-35391 · CVE-2023-35788 · CVE-2023-35823 · CVE-2023-35824 · CVE-2023-35828 · CVE-2023-35829 · CVE-2023-36038 · CVE-2023-36049 · CVE-2023-36435 · CVE-2023-36558 · CVE-2023-36792 · CVE-2023-36793 · CVE-2023-36794 · CVE-2023-36796 · CVE-2023-36799 · CVE-2023-38171 · CVE-2023-38178 · CVE-2023-38180 · CVE-2023-38380 · CVE-2023-38533 · CVE-2023-39615 · CVE-2023-41910 · CVE-2023-44317 · CVE-2023-44318 · CVE-2023-44319 · CVE-2023-44373 · CVE-2023-44374 · CVE-2023-44487 · CVE-2023-49691 · CVE-2023-50763 · CVE-2023-52474 · CVE-2024-0775 · CVE-2024-31484 · CVE-2024-33500 · CVE-2024-35206 · CVE-2024-35207 · CVE-2024-35208 · CVE-2024-35209 · CVE-2024-35210 · CVE-2024-35211 · CVE-2024-35212 · CVE-2024-35292 · CVE-2024-35303 · CVE-2024-36266 · CVE-2021-47178 · CVE-2022-1015 · CVE-2022-2097 · CVE-2022-3435 · CVE-2022-3545 · CVE-2022-3623 · CVE-2022-3643 · CVE-2022-4304 · CVE-2022-4450 · CVE-2022-36323 · CVE-2022-39189 · CVE-2022-40225 · CVE-2022-40303 · CVE-2022-40304 · CVE-2022-41742 · CVE-2022-42328 · CVE-2022-42329 · CVE-2022-44792 · CVE-2022-44793 · CVE-2022-45886 · CVE-2022-45887 · CVE-2022-45919 · CVE-2022-46144 · CVE-2023-0160 · CVE-2023-0215 · CVE-2023-0286 · CVE-2023-0464 · CVE-2023-0465 · CVE-2023-0466 · CVE-2023-1017 · CVE-2023-2124 · CVE-2023-2269 · CVE-2023-3446 · CVE-2023-3817 · CVE-2023-5678 · CVE-2023-21255 · CVE-2023-21808 · CVE-2023-24895 · CVE-2023-24897 · CVE-2023-24936 · CVE-2023-26552 · CVE-2023-26553 · CVE-2023-26554 · CVE-2023-27321 · CVE-2023-28260

SSA-341067: SSA-341067: Multiple vulnerabilities in third-party components in ST7 ScadaConnect before V1.1

CVE-2022-40303 · CVE-2022-40304 · CVE-2023-0464 · CVE-2023-0465 · CVE-2023-0466 · CVE-2023-3446 · CVE-2023-5678 · CVE-2023-21808 · CVE-2023-24895 · CVE-2023-24897 · CVE-2023-24936 · CVE-2023-28260 · CVE-2023-28484 · CVE-2023-29331 · CVE-2023-29469 · CVE-2023-32032 · CVE-2023-33126 · CVE-2023-33127 · CVE-2023-33128 · CVE-2023-33135 · CVE-2023-33170 · CVE-2023-35390 · CVE-2023-35391 · CVE-2023-36038 · CVE-2023-36049 · CVE-2023-36435 · CVE-2023-36558 · CVE-2023-36792 · CVE-2023-36793 · CVE-2023-36794 · CVE-2023-36796 · CVE-2023-36799 · CVE-2023-38171 · CVE-2023-38178 · CVE-2023-38180 · CVE-2023-39615 · CVE-2023-44487

ICSA-24-165-04: Siemens ST7 ScadaConnect

CVE-2022-40303 · CVE-2022-40304 · CVE-2023-0464 · CVE-2023-0465 · CVE-2023-0466 · CVE-2023-3446 · CVE-2023-5678 · CVE-2023-21808 · CVE-2023-24895 · CVE-2023-24897 · CVE-2023-24936 · CVE-2023-28260 · CVE-2023-28484 · CVE-2023-29331 · CVE-2023-29469 · CVE-2023-32032 · CVE-2023-33126 · CVE-2023-33127 · CVE-2023-33128 · CVE-2023-33135 · CVE-2023-33170 · CVE-2023-35390 · CVE-2023-35391 · CVE-2023-36038 · CVE-2023-36049 · CVE-2023-36435 · CVE-2023-36558 · CVE-2023-36792 · CVE-2023-36793 · CVE-2023-36794 · CVE-2023-36796 · CVE-2023-36799 · CVE-2023-38171 · CVE-2023-38178 · CVE-2023-38180 · CVE-2023-39615 · CVE-2023-44487

msrc_CVE-2023-35391: ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

CVE-2023-35391

Source published
Aug 8, 2023, 6:52:30 PM (timezone not stated)
Source modified
Aug 10, 2026, 3:11:59 PM (timezone not stated)
Saved here
22 Nov 2026 06:31:37 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C

nvd · CVE-2023-35391

Published

ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: NVD-CWE-noinfo

Original publisher date fields

published: 2023-08-08T19:15:09.940

lastModified: 2026-08-10T16:18:28.717

3 source CPE criteria · context only
  • cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:asp.net_core:*:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
8 Aug 2023 19:15:09 UTC
Source modified
10 Aug 2026 16:18:28 UTC
Saved here
24 Oct 2026 22:17:15 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS 3.1 · [email protected] · Primary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

osv · GHSA-j8rm-cm55-qqj6

Published

.NET Information Disclosure Vulnerability

# Microsoft Security Advisory CVE-2023-35391: .NET Information Disclosure Vulnerability ## <a name="executive-summary"></a>Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET core 2.1, .NET 6.0 and, .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in ASP.NET Core 2.1, .NET 6.0 and, .NET 7.0 applications using SignalR when redis backplane use might result in information disclosure. ## Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/267 ### <a name="mitigation-factors"></a>Mitigation factors Microsoft has not identified any mitigating factors for this vulnerability. ## <a name="affected-software"></a>Affected software * Any .NET 7.0 application running on .NET 7.0.9 or earlier. * Any .NET 6.0 application running on .NET 6.0.20 or earlier. If your application uses the following package versions, ensure you update to the latest version of .NET. ### <a name=".NET 7"></a>.NET 7 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.AspNetCore.SignalR.StackExchangeRedis](https://www.nuget.org/packages/Microsoft.AspNetCore.SignalR.StackExchangeRedis) | >= 7.0.0, <= 7.0.9 | 7.0.10 ### <a name=".NET 6"></a>.NET 6 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.AspNetCore.SignalR.StackExchangeRedis](https://www.nuget.org/packages/Microsoft.AspNetCore.SignalR.StackExchangeRedis) | >= 6.0.0, <= 6.0.20 | 6.0.21 ### <a name="ASP.NET Core 2.1"></a>ASP.NET Core 2.1 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.AspNetCore.SignalR.Redis](https://www.nuget.org/packages/Microsoft.AspNetCore.SignalR.Redis) | < 1.0.40 | 1.0.40 ## Advisory FAQ ### <a name="how-affected"></a>How do I know if I am affected? If you have a runtime or SDK with a version listed, or an affected package listed in [affected software](#affected-software), you're exposed to the vulnerability. ### <a name="how-fix"></a>How do I fix the issue? * To fix the issue please install the latest version of .NET 6.0 or .NET 7.0. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs. * If you are using one of the affected packages, please update to the patched version listed above. * If you have .NET 6.0 or greater installed, you can list the versions you have installed by running the `dotnet --info` command. You will see output like the following; ``` .NET Core SDK (reflecting any global.json): Version: 6.0.300 Commit: 8473146e7d Runtime Environment: OS Name: Windows OS Version: 10.0.18363 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\6.0.300\ Host (useful for support): Version: 6.0.5 Commit: 8473146e7d .NET Core SDKs installed: 6.0.300 [C:\Program Files\dotnet\sdk] .NET Core runtimes installed: Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] To install additional .NET Core runtimes or SDKs: https://aka.ms/dotnet-download ``` * If you're using .NET 7.0, you should download and install Runtime 7.0.10 or SDK 7.0.110 (for Visual Studio 2022 v17.4) from https://dotnet.microsoft.com/download/dotnet-core/7.0. * If you're using .NET 6.0, you should download and install Runtime 6.0.21 or SDK 6.0.316 (for Visual Studio 2022 v17.2) from https://dotnet.microsoft.com/download/dotnet-core/6.0. .NET 6.0 and and .NET 7.0 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates. Once you have installed the updated runtime or SDK, restart your apps for the update to take effect. Additionally, if you've deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. ## Other Information ### Reporting Security Issues If you have found a potential security issue in .NET 6.0 or .NET 7.0, please email details to [email protected]. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at <https://aka.ms/corebounty>. ### Support You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue. ### Disclaimer The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. ### External Links [CVE-2023-35391]( https://www.cve.org/CVERecord?id=CVE-2023-35391) ### Revisions V1.0 (August 08, 2023): Advisory published. _Version 1.0_ _Last Updated 2023-08-08_

Source published
11 Aug 2023 20:54:45 UTC
Source modified
16 Feb 2024 08:24:44 UTC
Saved here
23 Oct 2026 16:01:25 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Publisher rating · HIGH

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 11:16 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current