libgit2 up to 0.26.1 index.c read_entry integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in libgit2 up to 0.26.1. This vulnerability affects the function read_entry of the file index.c. The manipulation leads to integer overflow.
This vulnerability is documented as CVE-2018-8098. The attack can be initiated remotely. There is not any exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in libgit2 up to 0.26.1. This issue affects the function read_entry of the file index.c. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Integer overflow in the index.c:read_entry() function while decompressing a compressed prefix length in libgit2 before v0.26.2 allows an attacker to cause a denial of service (out-of-bounds read) via a crafted repository index file.
The bug was discovered 03/08/2018. The weakness was released 03/14/2018 (GitHub Repository). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2018-8098 since 03/13/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 of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 0.26.2 eliminates this vulnerability.
Entry connected to this vulnerability is available at VDB-114492. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/libgit2/libgit2/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: Integer overflowCWE: CWE-190 / CWE-189
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: libgit2 0.26.2
Patch: github.com
Timeline
03/08/2018 🔍03/13/2018 🔍
03/13/2018 🔍
03/14/2018 🔍
03/14/2018 🔍
02/21/2023 🔍
Sources
Product: github.comAdvisory: 3207ddb0103543da8ad2139ec6539f590f9900c1
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-8098 (🔍)
GCVE (CVE): GCVE-0-2018-8098
GCVE (VulDB): GCVE-100-114491
See also: 🔍
Entry
Created: 03/14/2018 09:38Updated: 02/21/2023 17:16
Changes: 03/14/2018 09:38 (59), 01/13/2020 09:48 (2), 02/21/2023 17:09 (5), 02/21/2023 17:16 (1)
Complete: 🔍
Cache ID: 216:D8F:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.