rpm package
almalinux/curl
pkg:rpm/almalinux/curl
Vulnerabilities (27)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2025-9086 | Hig | 7.5 | < 7.61.1-34.el8_10.9 | 7.61.1-34.el8_10.9 | Sep 12, 2025 | 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 | |
| CVE-2024-2398 | — | < 7.76.1-29.el9_4.1 | 7.76.1-29.el9_4.1 | Mar 27, 2024 | When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated head | ||
| CVE-2023-46218 | Med | 6.5 | < 7.76.1-26.el9_3.3 | 7.76.1-26.el9_3.3 | Dec 7, 2023 | This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains. It could do this | |
| CVE-2023-38546 | Low | 3.7 | < 7.76.1-23.el9_2.4 | 7.76.1-23.el9_2.4 | Oct 18, 2023 | 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 | |
| CVE-2023-38545 | Cri | 9.8 | < 7.76.1-23.el9_2.4 | 7.76.1-23.el9_2.4 | Oct 18, 2023 | 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 byt | |
| CVE-2023-28322 | — | < 7.76.1-23.el9_2.2 | 7.76.1-23.el9_2.2 | May 26, 2023 | An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was | ||
| CVE-2023-28321 | — | < 7.76.1-23.el9_2.2 | 7.76.1-23.el9_2.2 | May 26, 2023 | An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provi | ||
| CVE-2023-27538 | — | < 7.76.1-26.el9 | 7.76.1-26.el9 | Mar 30, 2023 | An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse t | ||
| CVE-2023-27536 | — | < 7.61.1-30.el8_8.3 | 7.61.1-30.el8_8.3 | Mar 30, 2023 | An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affect | ||
| CVE-2023-27535 | — | < 7.76.1-23.el9_2.1 | 7.76.1-23.el9_2.1 | Mar 30, 2023 | An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. | ||
| CVE-2023-27534 | — | < 7.76.1-26.el9 | 7.76.1-26.el9 | Mar 30, 2023 | A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home dire | ||
| CVE-2023-27533 | — | < 7.76.1-26.el9 | 7.76.1-26.el9 | Mar 30, 2023 | A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send cont | ||
| CVE-2023-23916 | — | < 7.61.1-25.el8_7.3 | 7.61.1-25.el8_7.3 | Feb 23, 2023 | An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "li | ||
| CVE-2022-43552 | — | < 7.76.1-23.el9 | 7.76.1-23.el9 | Feb 9, 2023 | A use after free vulnerability exists in curl <7.87.0. Curl can be asked to *tunnel* virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl wo | ||
| CVE-2022-32221 | — | < 7.76.1-19.el9_1.1 | 7.76.1-19.el9_1.1 | Dec 5, 2022 | When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was used to issue a `PUT` request which used that callback. This f | ||
| CVE-2022-35252 | — | < 7.76.1-23.el9 | 7.76.1-23.el9 | Sep 23, 2022 | When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings. | ||
| CVE-2022-32208 | — | < 7.76.1-14.el9_0.5 | 7.76.1-14.el9_0.5 | Jul 7, 2022 | When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client. | ||
| CVE-2022-32207 | — | < 7.76.1-14.el9_0.5 | 7.76.1-14.el9_0.5 | Jul 7, 2022 | When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a rename from a temporary name to the final target file name.In that rename operation, it might accidentally *widen* the permissions for the targ | ||
| CVE-2022-32206 | — | < 7.76.1-14.el9_0.5 | 7.76.1-14.el9_0.5 | Jul 7, 2022 | curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to ins | ||
| CVE-2022-27782 | Hig | 7.5 | < 7.61.1-22.el8_6.3 | 7.61.1-22.el8_6.3 | Jun 2, 2022 | libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, s |
- affected < 7.61.1-34.el8_10.9fixed 7.61.1-34.el8_10.9
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
- CVE-2024-2398Mar 27, 2024affected < 7.76.1-29.el9_4.1fixed 7.76.1-29.el9_4.1
When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated head
- affected < 7.76.1-26.el9_3.3fixed 7.76.1-26.el9_3.3
This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains. It could do this
- affected < 7.76.1-23.el9_2.4fixed 7.76.1-23.el9_2.4
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
- affected < 7.76.1-23.el9_2.4fixed 7.76.1-23.el9_2.4
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 byt
- CVE-2023-28322May 26, 2023affected < 7.76.1-23.el9_2.2fixed 7.76.1-23.el9_2.2
An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was
- CVE-2023-28321May 26, 2023affected < 7.76.1-23.el9_2.2fixed 7.76.1-23.el9_2.2
An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provi
- CVE-2023-27538Mar 30, 2023affected < 7.76.1-26.el9fixed 7.76.1-26.el9
An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse t
- CVE-2023-27536Mar 30, 2023affected < 7.61.1-30.el8_8.3fixed 7.61.1-30.el8_8.3
An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affect
- CVE-2023-27535Mar 30, 2023affected < 7.76.1-23.el9_2.1fixed 7.76.1-23.el9_2.1
An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup.
- CVE-2023-27534Mar 30, 2023affected < 7.76.1-26.el9fixed 7.76.1-26.el9
A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home dire
- CVE-2023-27533Mar 30, 2023affected < 7.76.1-26.el9fixed 7.76.1-26.el9
A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send cont
- CVE-2023-23916Feb 23, 2023affected < 7.61.1-25.el8_7.3fixed 7.61.1-25.el8_7.3
An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "li
- CVE-2022-43552Feb 9, 2023affected < 7.76.1-23.el9fixed 7.76.1-23.el9
A use after free vulnerability exists in curl <7.87.0. Curl can be asked to *tunnel* virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl wo
- CVE-2022-32221Dec 5, 2022affected < 7.76.1-19.el9_1.1fixed 7.76.1-19.el9_1.1
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was used to issue a `PUT` request which used that callback. This f
- CVE-2022-35252Sep 23, 2022affected < 7.76.1-23.el9fixed 7.76.1-23.el9
When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings.
- CVE-2022-32208Jul 7, 2022affected < 7.76.1-14.el9_0.5fixed 7.76.1-14.el9_0.5
When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client.
- CVE-2022-32207Jul 7, 2022affected < 7.76.1-14.el9_0.5fixed 7.76.1-14.el9_0.5
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a rename from a temporary name to the final target file name.In that rename operation, it might accidentally *widen* the permissions for the targ
- CVE-2022-32206Jul 7, 2022affected < 7.76.1-14.el9_0.5fixed 7.76.1-14.el9_0.5
curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to ins
- affected < 7.61.1-22.el8_6.3fixed 7.61.1-22.el8_6.3
libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, s
Page 1 of 2