libsolv up to 0.7.2 src/pool.h pool_whatprovides resource management ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in libsolv up to 0.7.2. Affected is the function pool_whatprovides of the file src/pool.h. The manipulation leads to resource management.
This vulnerability is documented as CVE-2018-20534. The attack can be initiated remotely. There is not any exploit available.
The existence of this vulnerability is still disputed at present.
Details
A vulnerability was found in libsolv up to 0.7.2. It has been rated as problematic. This issue affects the function pool_whatprovides of the file src/pool.h. The manipulation with an unknown input leads to a resource management vulnerability. Using CWE to declare the problem leads to CWE-399. Impacted is availability. The summary by CVE is:
There is an illegal address access at src/pool.h (function pool_whatprovides) in libsolv.a in libsolv through 0.7.2 that will cause a denial of service.
The bug was discovered 12/13/2018. The weakness was released 12/28/2018 (Website). The advisory is shared at bugzilla.redhat.com. The identification of this vulnerability is CVE-2018-20534 since 12/27/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 15 days. During that time the estimated underground price was around $0-$5k. The real existence of this vulnerability is still doubted at the moment. The commercial vulnerability scanner Qualys is able to test this issue with plugin 197400 (Ubuntu Security Notification for Libsolv Vulnerabilities (USN-3916-1)).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-128499 and VDB-128500. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.8VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 6.5
CNA 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: Resource managementCWE: CWE-399 / 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 |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
12/13/2018 🔍12/27/2018 🔍
12/28/2018 🔍
12/28/2018 🔍
12/29/2018 🔍
08/05/2024 🔍
Sources
Advisory: RHSA-2019:2290Status: Confirmed
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2018-20534 (🔍)
GCVE (CVE): GCVE-0-2018-20534
GCVE (VulDB): GCVE-100-128501
See also: 🔍
Entry
Created: 12/29/2018 17:26Updated: 08/05/2024 23:09
Changes: 12/29/2018 17:26 (59), 04/24/2020 21:00 (2), 06/22/2023 11:17 (4), 08/05/2024 23:09 (29)
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.