| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in tendermint. It has been classified as problematic. Affected by this issue is some unknown functionality of the component Response Body Handler. Performing a manipulation results in resource consumption. This vulnerability is identified as CVE-2019-25072. The attack can be initiated remotely. There is not any exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as problematic, was found in tendermint (unknown version). This affects an unknown code block of the component Response Body Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:
Due to support of Gzip compression in request bodies, as well as a lack of limiting response body sizes, a malicious server can cause a client to consume a significant amount of system resources, which may be used as a denial of service vector.
The weakness was released 12/28/2022. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2019-25072 since 07/29/2022. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Applying the patch 03085c2da23b179c4a51f59a03cb40aa4e85a613 is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 03085c2da23b179c4a51f59a03cb40aa4e85a613
Timeline
07/29/2022 🔍12/28/2022 🔍
12/28/2022 🔍
04/11/2025 🔍
Sources
Product: github.comAdvisory: 03085c2da23b179c4a51f59a03cb40aa4e85a613
Status: Confirmed
CVE: CVE-2019-25072 (🔍)
GCVE (CVE): GCVE-0-2019-25072
GCVE (VulDB): GCVE-100-216921
Entry
Created: 12/28/2022 09:13Updated: 04/11/2025 19:34
Changes: 12/28/2022 09:13 (39), 01/25/2023 11:13 (1), 01/25/2023 11:20 (11), 04/11/2025 19:34 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.