| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in HTTP2. Affected is an unknown function of the component Push Handler. The manipulation as part of Request results in memory corruption. This vulnerability is identified as CVE-2019-10081. The attack can be executed remotely. There is not any exploit available. Applying restrictive firewalling is recommended.
Details
A vulnerability, which was classified as problematic, was found in HTTP2. Affected is an unknown functionality of the component Push Handler. The manipulation as part of a Request leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on availability. CVE summarizes:
HTTP/2 (2.4.20 through 2.4.39) very early pushes, for example configured with "H2PushResource", could lead to an overwrite of memory in the pushing request's pool, leading to crashes. The memory copied is that of the configured push link header values, not data supplied by the client.
The weakness was released 08/15/2019 (Website). The advisory is available at seclists.org. This vulnerability is traded as CVE-2019-10081 since 03/26/2019. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.
It is possible to mitigate the weakness by firewalling .
Entry connected to this vulnerability is available at VDB-142324. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
- 2.4.20
- 2.4.21
- 2.4.22
- 2.4.23
- 2.4.24
- 2.4.25
- 2.4.26
- 2.4.27
- 2.4.28
- 2.4.29
- 2.4.30
- 2.4.31
- 2.4.32
- 2.4.33
- 2.4.34
- 2.4.35
- 2.4.36
- 2.4.37
- 2.4.38
- 2.4.39
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.2
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: Memory corruptionCWE: CWE-119
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
03/26/2019 🔍08/15/2019 🔍
08/16/2019 🔍
11/25/2023 🔍
Sources
Advisory: K84341091Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-10081 (🔍)
GCVE (CVE): GCVE-0-2019-10081
GCVE (VulDB): GCVE-100-140106
See also: 🔍
Entry
Created: 08/16/2019 07:09Updated: 11/25/2023 15:41
Changes: 08/16/2019 07:09 (55), 07/29/2020 09:45 (2), 11/25/2023 15:35 (4), 11/25/2023 15:41 (1)
Complete: 🔍
Cache ID: 216:72D:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.