update: curl

[dongsupark]

Name: curl
CVEs: CVE-2023-38545, CVE-2023-38546
CVSSs: 9.8, 3.7
Action Needed: update to >= 8.3.0-r2 or >= 8.4.0

Summary:

• CVE-2023-38545: SOCKS5 heap buffer overflow. 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 is 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.
  • https://seclists.org/oss-sec/2023/q4/80
• CVE-2023-38546: cookie injection with none file. 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 en 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.
  • https://seclists.org/oss-sec/2023/q4/81

refmap.gentoo: https://bugs.gentoo.org/915195