Microsoft ASP.NET Core/.NET/Visual Studio information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Microsoft ASP.NET Core, .NET and Visual Studio. It has been rated as problematic. The impacted element is an unknown function. This manipulation causes information disclosure. This vulnerability is handled as CVE-2023-35391. It is possible to launch the attack on the local host. There is not any exploit available. It is recommended to apply a patch to fix this issue.
Details
A vulnerability has been found in Microsoft ASP.NET Core, .NET and Visual Studio (Programming Tool Software) (version unknown) and classified as problematic. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
The weakness was released 08/08/2023 as confirmed security guidance (Website). It is possible to read the advisory at portal.msrc.microsoft.com. This vulnerability is known as CVE-2023-35391. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 239977 (TencentOS Server 4: dotnet6.0 (TSSA-2024:0677)), which helps to determine the existence of the flaw in a target environment.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (239977). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.1
Vendor Vector (Microsoft): 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 7.1
CNA Vector (Microsoft): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 239977
Nessus Name: TencentOS Server 4: dotnet6.0 (TSSA-2024:0677)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
06/14/2023 🔍08/08/2023 🔍
08/08/2023 🔍
08/08/2023 🔍
06/17/2025 🔍
Sources
Vendor: microsoft.comAdvisory: portal.msrc.microsoft.com
Status: Confirmed
CVE: CVE-2023-35391 (🔍)
GCVE (CVE): GCVE-0-2023-35391
GCVE (VulDB): GCVE-100-236551
Entry
Created: 08/08/2023 20:51Updated: 06/17/2025 20:34
Changes: 08/08/2023 20:51 (7), 08/08/2023 20:52 (25), 08/08/2023 20:55 (22), 09/02/2023 07:32 (1), 09/02/2023 07:37 (20), 06/17/2025 20:34 (17)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.