curl up to 7.83.x HTTP Compression allocation of resources

Summaryinfo

A vulnerability was found in curl up to 7.83.x. It has been rated as problematic. Affected by this vulnerability is an unknown functionality of the component HTTP Compression Handler. The manipulation leads to allocation of resources. This vulnerability is uniquely identified as CVE-2022-32206. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in curl up to 7.83.x (Network Utility Software). This issue affects an unknown function of the component HTTP Compression Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. The summary by CVE is:

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.

The weakness was disclosed 07/07/2022. The advisory is shared at hackerone.com. The identification of this vulnerability is CVE-2022-32206 since 06/01/2022. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 7.84.0 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Network Utility Software

Name

• curl

Version

• 7.0
• 7.1
• 7.2
• 7.3
• 7.4
• 7.5
• 7.6
• 7.7
• 7.8
• 7.9
• 7.10
• 7.11
• 7.12
• 7.13
• 7.14
• 7.15
• 7.16
• 7.17
• 7.18
• 7.19
• 7.20
• 7.21
• 7.22
• 7.23
• 7.24
• 7.25
• 7.26
• 7.27
• 7.28
• 7.29
• 7.30
• 7.31
• 7.32
• 7.33
• 7.34
• 7.35
• 7.36
• 7.37
• 7.38
• 7.39
• 7.40
• 7.41
• 7.42
• 7.43
• 7.44
• 7.45
• 7.46
• 7.47
• 7.48
• 7.49
• 7.50
• 7.51
• 7.52
• 7.53
• 7.54
• 7.55
• 7.56
• 7.57
• 7.58
• 7.59
• 7.60
• 7.61
• 7.62
• 7.63
• 7.64
• 7.65
• 7.66
• 7.67
• 7.68
• 7.69
• 7.70
• 7.71
• 7.72
• 7.73
• 7.74
• 7.75
• 7.76
• 7.77
• 7.78
• 7.79
• 7.80
• 7.81
• 7.82
• 7.83

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion