Apple SwiftNIO HTTP Body Decompression unchecked input for loop condition

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Apple SwiftNIO. The affected element is an unknown function of the component HTTP Body Decompression Handler. Performing a manipulation results in unchecked input for loop condition. This vulnerability is cataloged as CVE-2022-3252. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in Apple SwiftNIO (affected version unknown). This affects an unknown functionality of the component HTTP Body Decompression Handler. The manipulation with an unknown input leads to a unchecked input for loop condition vulnerability. CWE is classifying the issue as CWE-606. The product does not properly check inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping. This is going to have an impact on availability. The summary by CVE is:

Improper detection of complete HTTP body decompression SwiftNIO Extras provides a pair of helpers for transparently decompressing received HTTP request or response bodies. These two objects (HTTPRequestDecompressor and HTTPResponseDecompressor) both failed to detect when the decompressed body was considered complete. If trailing junk data was appended to the HTTP message body, the code would repeatedly attempt to decompress this data and fail. This would lead to an infinite loop making no forward progress, leading to livelock of the system and denial-of-service. This issue can be triggered by any attacker capable of sending a compressed HTTP message. Most commonly this is HTTP servers, as compressed HTTP messages cannot be negotiated for HTTP requests, but it is possible that users have configured decompression for HTTP requests as well. The attack is low effort, and likely to be reached without requiring any privilege or system access. The impact on availability is high: the process immediately becomes unavailable but does not immediately crash, meaning that it is possible for the process to remain in this state until an administrator intervenes or an automated circuit breaker fires. If left unchecked this issue will very slowly exhaust memory resources due to repeated buffer allocation, but the buffers are not written to and so it is possible that the processes will not terminate for quite some time. This risk can be mitigated by removing transparent HTTP message decompression. The issue is fixed by correctly detecting the termination of the compressed body as reported by zlib and refusing to decompress further data. The issue was found by Vojtech Rylko (https://github.com/vojtarylko) and reported publicly on GitHub.

The weakness was shared 09/22/2022 as GHSA-773g-x274-8qmf. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-3252 since 09/20/2022. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/22/2022). The attack technique deployed by this issue is T1449 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Apple

Name

• SwiftNIO

License

• commercial

Website

• Vendor: https://www.apple.com/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion