| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Microsoft ASP.NET Core 2.2. This impacts an unknown function. Performing a manipulation as part of Request results in data processing. This vulnerability is reported as CVE-2019-0815. The attack is possible to be carried out remotely. No exploit exists. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Microsoft ASP.NET Core 2.2. It has been classified as problematic. This affects an unknown functionality. The manipulation as part of a Request leads to a data processing vulnerability. CWE is classifying the issue as CWE-19. This is going to have an impact on availability. The summary by CVE is:
A denial of service vulnerability exists when ASP.NET Core improperly handles web requests, aka 'ASP.NET Core Denial of Service Vulnerability'.
The bug was discovered 04/09/2019. The weakness was disclosed 04/09/2019 as confirmed security update guide (Website). The advisory is shared at portal.msrc.microsoft.com. The public release has been coordinated in cooperation with Microsoft. This vulnerability is uniquely identified as CVE-2019-0815 since 11/26/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The advisory points out:
A denial of service vulnerability exists when ASP.NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 91524 (Microsoft ASP.NET Core Denial Of Service Vulnerability April 2019).
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Data processingCWE: CWE-19
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
11/26/2018 🔍04/09/2019 🔍
04/09/2019 🔍
04/09/2019 🔍
04/10/2019 🔍
08/28/2023 🔍
Sources
Vendor: microsoft.comAdvisory: portal.msrc.microsoft.com
Status: Confirmed
Coordinated: 🔍
CVE: CVE-2019-0815 (🔍)
GCVE (CVE): GCVE-0-2019-0815
GCVE (VulDB): GCVE-100-133197
SecurityFocus: 107701
Entry
Created: 04/10/2019 07:17Updated: 08/28/2023 07:08
Changes: 04/10/2019 07:17 (61), 05/28/2020 08:07 (3), 08/28/2023 07:08 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.