An update for curl is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP3,openEuler-22.03-LTS,openEuler-22.03-LTS-SP1 and openEuler-22.03-LTS-SP2 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2023-1762 Final 1.0 1.0 2023-10-23 Initial 2023-10-23 2023-10-23 openEuler SA Tool V1.0 2023-10-23 curl security update An update for curl is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP3,openEuler-22.03-LTS,openEuler-22.03-LTS-SP1 and openEuler-22.03-LTS-SP2. cURL is a computer software project providing a library (libcurl) and command-line tool (curl) for transferring data using various protocols. Security Fix(es): This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this 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 host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with. (CVE-2023-38545) 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](https://curl.se/libcurl/c/curl_easy_duphandle.html). 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. (CVE-2023-38546) An update for curl is now available for openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP3,openEuler-22.03-LTS,openEuler-22.03-LTS-SP1 and openEuler-22.03-LTS-SP2. openEuler Security has rated this update as having a security impact of high. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. High curl https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1762 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-38545 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-38546 https://nvd.nist.gov/vuln/detail/CVE-2023-38545 https://nvd.nist.gov/vuln/detail/CVE-2023-38546 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP3 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 curl-debuginfo-7.71.1-31.oe1.aarch64.rpm libcurl-7.71.1-31.oe1.aarch64.rpm libcurl-devel-7.71.1-31.oe1.aarch64.rpm curl-7.71.1-31.oe1.aarch64.rpm curl-debugsource-7.71.1-31.oe1.aarch64.rpm curl-7.71.1-31.oe1.aarch64.rpm libcurl-7.71.1-31.oe1.aarch64.rpm libcurl-devel-7.71.1-31.oe1.aarch64.rpm curl-debuginfo-7.71.1-31.oe1.aarch64.rpm curl-debugsource-7.71.1-31.oe1.aarch64.rpm curl-7.79.1-24.oe2203.aarch64.rpm curl-debuginfo-7.79.1-24.oe2203.aarch64.rpm libcurl-devel-7.79.1-24.oe2203.aarch64.rpm libcurl-7.79.1-24.oe2203.aarch64.rpm curl-debugsource-7.79.1-24.oe2203.aarch64.rpm curl-debuginfo-7.79.1-24.oe2203sp1.aarch64.rpm libcurl-devel-7.79.1-24.oe2203sp1.aarch64.rpm libcurl-7.79.1-24.oe2203sp1.aarch64.rpm curl-debugsource-7.79.1-24.oe2203sp1.aarch64.rpm curl-7.79.1-24.oe2203sp1.aarch64.rpm curl-debuginfo-7.79.1-24.oe2203sp2.aarch64.rpm curl-7.79.1-24.oe2203sp2.aarch64.rpm libcurl-7.79.1-24.oe2203sp2.aarch64.rpm curl-debugsource-7.79.1-24.oe2203sp2.aarch64.rpm libcurl-devel-7.79.1-24.oe2203sp2.aarch64.rpm curl-help-7.71.1-31.oe1.noarch.rpm curl-help-7.71.1-31.oe1.noarch.rpm curl-help-7.79.1-24.oe2203.noarch.rpm curl-help-7.79.1-24.oe2203sp1.noarch.rpm curl-help-7.79.1-24.oe2203sp2.noarch.rpm curl-7.71.1-31.oe1.src.rpm curl-7.71.1-31.oe1.src.rpm curl-7.79.1-24.oe2203.src.rpm curl-7.79.1-24.oe2203sp1.src.rpm curl-7.79.1-24.oe2203sp2.src.rpm curl-7.71.1-31.oe1.x86_64.rpm libcurl-7.71.1-31.oe1.x86_64.rpm curl-debugsource-7.71.1-31.oe1.x86_64.rpm libcurl-devel-7.71.1-31.oe1.x86_64.rpm curl-debuginfo-7.71.1-31.oe1.x86_64.rpm curl-debuginfo-7.71.1-31.oe1.x86_64.rpm curl-debugsource-7.71.1-31.oe1.x86_64.rpm curl-7.71.1-31.oe1.x86_64.rpm libcurl-7.71.1-31.oe1.x86_64.rpm libcurl-devel-7.71.1-31.oe1.x86_64.rpm curl-debuginfo-7.79.1-24.oe2203.x86_64.rpm libcurl-devel-7.79.1-24.oe2203.x86_64.rpm curl-debugsource-7.79.1-24.oe2203.x86_64.rpm curl-7.79.1-24.oe2203.x86_64.rpm libcurl-7.79.1-24.oe2203.x86_64.rpm libcurl-devel-7.79.1-24.oe2203sp1.x86_64.rpm curl-7.79.1-24.oe2203sp1.x86_64.rpm libcurl-7.79.1-24.oe2203sp1.x86_64.rpm curl-debuginfo-7.79.1-24.oe2203sp1.x86_64.rpm curl-debugsource-7.79.1-24.oe2203sp1.x86_64.rpm curl-7.79.1-24.oe2203sp2.x86_64.rpm libcurl-devel-7.79.1-24.oe2203sp2.x86_64.rpm libcurl-7.79.1-24.oe2203sp2.x86_64.rpm curl-debugsource-7.79.1-24.oe2203sp2.x86_64.rpm curl-debuginfo-7.79.1-24.oe2203sp2.x86_64.rpm This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this 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 host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with. 2023-10-23 CVE-2023-38545 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP3 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 High 7.5 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H curl security update 2023-10-23 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1762 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](https://curl.se/libcurl/c/curl_easy_duphandle.html). 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. 2023-10-23 CVE-2023-38546 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP3 openEuler-22.03-LTS openEuler-22.03-LTS-SP1 openEuler-22.03-LTS-SP2 Medium 5.0 AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L curl security update 2023-10-23 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1762