whoopsie whoopsie.c parse_report resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in whoopsie. It has been declared as problematic. Impacted is the function parse_report of the file whoopsie.c. Executing a manipulation can lead to resource consumption.
This vulnerability is registered as CVE-2020-11937. The attack needs to be launched locally. No exploit is available.
It is recommended to upgrade the affected component.
Details
A vulnerability has been found in whoopsie and classified as problematic. This vulnerability affects the function parse_report of the file whoopsie.c. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability. CVE summarizes:
In whoopsie, parse_report() from whoopsie.c allows a local attacker to cause a denial of service via a crafted file. The DoS is caused by resource exhaustion due to a memory leak. Fixed in 0.2.52.5ubuntu0.5, 0.2.62ubuntu0.5 and 0.2.69ubuntu0.1.
The weakness was published 08/06/2020 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability was named CVE-2020-11937 since 04/20/2020. The attack needs to be approached locally. Required for exploitation is a single authentication. There are known technical details, but no exploit is available.
Upgrading to version 0.2.52.5ubuntu0.5, 0.2.62ubuntu0.5 or 0.2.69ubuntu0.1 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.2
VulDB Base Score: 3.3
VulDB Temp Score: 2.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.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: Partially
Local: Yes
Remote: No
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: whoopsie 0.2.52.5ubuntu0.5/0.2.62ubuntu0.5/0.2.69ubuntu0.1
Timeline
04/20/2020 🔍08/06/2020 🔍
08/07/2020 🔍
11/07/2020 🔍
Sources
Advisory: github.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-11937 (🔍)
GCVE (CVE): GCVE-0-2020-11937
GCVE (VulDB): GCVE-100-159340
Entry
Created: 08/07/2020 08:27Updated: 11/07/2020 09:33
Changes: 08/07/2020 08:27 (38), 08/07/2020 08:32 (11), 11/07/2020 09:30 (1), 11/07/2020 09:33 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.