libcURL up to 8.6.0/8.7.0/8.7.1/8.8.0 ASN1 Parser utf8asn1str free of memory not on the heap
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libcURL up to 8.6.0/8.7.0/8.7.1/8.8.0. It has been classified as problematic. Affected by this issue is the function utf8asn1str of the component ASN1 Parser. Performing a manipulation results in free of memory not on the heap.
This vulnerability is identified as CVE-2024-6197. The attack can be initiated remotely. There is not any exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, was found in libcURL up to 8.6.0/8.7.0/8.7.1/8.8.0. This affects the function utf8asn1str of the component ASN1 Parser. The manipulation with an unknown input leads to a free of memory not on the heap vulnerability. CWE is classifying the issue as CWE-590. The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc(). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
libcurl's ASN1 parser has this utf8asn1str() function used for parsing an ASN.1 UTF-8 string. Itcan detect an invalid field and return error. Unfortunately, when doing so it also invokes `free()` on a 4 byte localstack buffer. Most modern malloc implementations detect this error and immediately abort. Some however accept the input pointer and add that memory to its list of available chunks. This leads to the overwriting of nearby stack memory. The content of the overwrite is decided by the `free()` implementation; likely to be memory pointers and a set of flags. The most likely outcome of exploting this flaw is a crash, although it cannot be ruled out that more serious results can be had in special circumstances.
The weakness was released by Z2_. The advisory is shared at curl.se. This vulnerability is uniquely identified as CVE-2024-6197 since 06/20/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 207713 (Nessus Network Monitor < 6.5.0 Multiple Vulnerabilities (TNS-2024-17)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 8.9.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (207713). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 7.5
CNA Vector (curl): 🔍
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: Free of memory not on the heapCWE: CWE-590
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 |
Nessus ID: 207713
Nessus Name: Nessus Network Monitor < 6.5.0 Multiple Vulnerabilities (TNS-2024-17)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: libcURL 8.9.0
Timeline
06/20/2024 🔍07/24/2024 🔍
07/24/2024 🔍
03/16/2025 🔍
Sources
Advisory: curl.seResearcher: Z2_
Status: Confirmed
CVE: CVE-2024-6197 (🔍)
GCVE (CVE): GCVE-0-2024-6197
GCVE (VulDB): GCVE-100-272361
Entry
Created: 07/24/2024 11:39Updated: 03/16/2025 21:11
Changes: 07/24/2024 11:39 (56), 07/24/2024 14:22 (1), 08/26/2024 21:25 (20), 09/30/2024 12:25 (2), 03/16/2025 21:11 (3)
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.