VIP AuthHub advisory for Curl vulnerability
Article ID: 275098
Updated On:
Products
Issue/Introduction
CVE-2023-38545 -SOCKS5 heap buffer overflow
A heap-based buffer overflow flaw in the SOCKS5 proxy handshake of the Curl package that could lead to arbitrary remote code execution when using SOCKS5 proxies to access untrusted web servers.
Severity: High
Affected versions: Curl and libcurl from 7.69.0 up to and including 8.3.0.
Description: This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake.
When curl is asked to pass along the hostname to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that hostname can be 255 bytes.
If the hostname is detected to be longer than 255 bytes, curl switches to local name resolving and instead passes on the resolved address only to the proxy. Due to a bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long hostname to the target buffer instead of copying just the resolved address there.
CVE-2023-38546 - Cookie injection with none file
It is a low severity vulnerability that only impacts libcurl – a library provided by the Curl project that allows developers to access Curl APIs from their own code.
Severity: Low
Affected versions: libcurl from 7.9.1 up to and including 8.3.0.
Description: This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.
libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers.
libcurl provides a function call that duplicates an easy handle called curl_easy_duphandle.
If a transfer has cookies enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned version of the handle would instead store the file name as none (using the four ASCII letters, no quotes).
Subsequent use of the cloned handle that does not explicitly set a source to load cookies from would then inadvertently load cookies from a file named none - if such a file exists and is readable in the current directory of the program using libcurl. And if using the correct file format of course.
Environment
AuthHub Version 2.1.5
Resolution
Impacted: Hazelcast Image (SSP Version 2.1.5)
Not Impacted: All other AuthHub Images (SSP Version 2.1.5)
Based on our initial review, the above mentioned docker images contain the vulnerable libcurl and curl packages. However, AuthHub never uses it in runtime. Also, AuthHub is deployed in controlled cloud environment where its less likely that login to the Hazelcast pod and try to make use of curl.
As a next step, Hazelcast image will be updated with the latest recommended version of curl library in upcoming Mid November release which is 2.2.
Additional Information
Third Party Vulnerability
Feedback
