LVM2 2.02 lvmetad-core.c vg_lookup release of resource ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in LVM2 2.02. The impacted element is the function vg_lookup of the file daemons/lvmetad/lvmetad-core.c. Performing a manipulation results in release of resource.
This vulnerability is identified as CVE-2020-8991. 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 classified as problematic has been found in LVM2 2.02. This affects the function vg_lookup of the file daemons/lvmetad/lvmetad-core.c. The manipulation with an unknown input leads to a release of resource vulnerability. CWE is classifying the issue as CWE-772. The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. This is going to have an impact on availability. The summary by CVE is:
vg_lookup in daemons/lvmetad/lvmetad-core.c in LVM2 2.02 mismanages memory, leading to an lvmetad memory leak, as demonstrated by running pvs. NOTE: RedHat disputes CVE-2020-8991 as not being a vulnerability since there’s no apparent route to either privilege escalation or to denial of service through the bug
The weakness was released 02/14/2020. This vulnerability is uniquely identified as CVE-2020-8991 since 02/14/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The real existence of this vulnerability is still doubted at the moment.
Applying the patch bcf9556b8fcd16ad8997f80cc92785f295c66701 is able to eliminate this problem.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.8
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 2.3
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: Release of resourceCWE: CWE-772 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: bcf9556b8fcd16ad8997f80cc92785f295c66701
Timeline
02/14/2020 🔍02/14/2020 🔍
02/14/2020 🔍
08/04/2024 🔍
Sources
Advisory: sourceware.orgStatus: Not defined
Disputed: 🔍
CVE: CVE-2020-8991 (🔍)
GCVE (CVE): GCVE-0-2020-8991
GCVE (VulDB): GCVE-100-150201
Entry
Created: 02/14/2020 09:54Updated: 08/04/2024 13:28
Changes: 02/14/2020 09:54 (35), 02/14/2020 09:59 (17), 03/31/2024 13:50 (19), 06/05/2024 10:30 (10), 08/04/2024 13:28 (4)
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.