Описание
ELSA-2026-1825: curl security update (MODERATE)
[8.12.1-2.el10_1.2]
- openssl: respect system crypto policy for TLS max version (RHEL-128923)
[8.12.1-2.el10_1.1]
- cookie: don't treat the leading slash as trailing (CVE-2025-9086) Resolves: RHEL-122689
Обновленные пакеты
Oracle Linux 10
Oracle Linux aarch64
curl
8.12.1-2.el10_1.2
libcurl
8.12.1-2.el10_1.2
libcurl-devel
8.12.1-2.el10_1.2
libcurl-minimal
8.12.1-2.el10_1.2
Oracle Linux x86_64
curl
8.12.1-2.el10_1.2
libcurl
8.12.1-2.el10_1.2
libcurl-devel
8.12.1-2.el10_1.2
libcurl-minimal
8.12.1-2.el10_1.2
Связанные CVE
Связанные уязвимости
1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with just a slash as path (`path=\"/\",`). Since this site is not secure, the cookie *should* just be ignored. 4. A bug in the path comparison logic makes curl read outside a heap buffer boundary The bug either causes a crash or it potentially makes the comparison come to the wrong conclusion and lets the clear-text site override the contents of the secure cookie, contrary to expectations and depending on the memory contents immediately following the single-byte allocation that holds the path. The presumed and correct behavior would be to plainly ignore the second set of the cookie since it was already set as secure on a secure host so overriding it on an insecure host should not be okay.
1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with just a slash as path (`path='/'`). Since this site is not secure, the cookie *should* just be ignored. 4. A bug in the path comparison logic makes curl read outside a heap buffer boundary The bug either causes a crash or it potentially makes the comparison come to the wrong conclusion and lets the clear-text site override the contents of the secure cookie, contrary to expectations and depending on the memory contents immediately following the single-byte allocation that holds the path. The presumed and correct behavior would be to plainly ignore the second set of the cookie since it was already set as secure on a secure host so overriding it on an insecure host should not be okay.
1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with just a slash as path (`path=\"/\",`). Since this site is not secure, the cookie *should* just be ignored. 4. A bug in the path comparison logic makes curl read outside a heap buffer boundary The bug either causes a crash or it potentially makes the comparison come to the wrong conclusion and lets the clear-text site override the contents of the secure cookie, contrary to expectations and depending on the memory contents immediately following the single-byte allocation that holds the path. The presumed and correct behavior would be to plainly ignore the second set of the cookie since it was already set as secure on a secure host so overriding it on an insecure host should not be okay.
1. A cookie is set using the `secure` keyword for `https://target` 2 ...