Vulnerability in ASP.NET Core SignalR and Visual Studio (CVE-2023-35391)
Summary
Vulnerability in ASP.NET Core SignalR and Visual Studio (CVE-2023-35391). Confidential information can be exposed externally.
Original description
The description as published by the source.
ASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2023-35391 was discovered in ASP.NET Core SignalR and Visual Studio.
Severity is Medium (CVSS 6.2/10). Exploitation requires specific conditions but can cause real harm if successful.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "ASP.NET Core SignalR and Visual Studio CVE-2023-35391".
CVE-2023-35391 (ASP.NET Core SignalR and Visual Studio). Severity: Medium / CVSSv3 6.2.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2023-35391) in ASP.NET Core SignalR and Visual Studio. A serious software flaw has been identified.
Target versions of ASP.NET Core SignalR and Visual Studio (see vendor advisory). If running in production, identify exposure immediately.
Severity: Medium (CVSS 6.2/10). Exploitation requires specific conditions but can cause real harm if successful.
Update to the patched release as listed in the vendor advisory.
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Affected packages
References
- patch msrc.microsoft.com
- web nvd.nist.gov