rpm package
suse/curl&distro=SUSE Linux Enterprise Module for Basesystem 15 SP4
pkg:rpm/suse/curl&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP4
Vulnerabilities (26)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-46219 | Med | 5.3 | < 8.0.1-150400.5.36.1 | 8.0.1-150400.5.36.1 | Dec 12, 2023 | When saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use. | |
| CVE-2023-46218 | Med | 6.5 | < 8.0.1-150400.5.36.1 | 8.0.1-150400.5.36.1 | 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 | < 8.0.1-150400.5.32.1 | 8.0.1-150400.5.32.1 | 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 | < 8.0.1-150400.5.32.1 | 8.0.1-150400.5.32.1 | 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-38039 | — | < 8.0.1-150400.5.29.1 | 8.0.1-150400.5.29.1 | Sep 15, 2023 | When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API. However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endles | ||
| CVE-2023-28322 | — | < 8.0.1-150400.5.23.1 | 8.0.1-150400.5.23.1 | 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 | — | < 8.0.1-150400.5.23.1 | 8.0.1-150400.5.23.1 | 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-28320 | — | < 8.0.1-150400.5.23.1 | 8.0.1-150400.5.23.1 | May 26, 2023 | A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using `alarm()` an | ||
| CVE-2023-28319 | — | < 8.0.1-150400.5.23.1 | 8.0.1-150400.5.23.1 | May 26, 2023 | A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now fre | ||
| CVE-2023-27538 | — | < 7.79.1-150400.5.18.1 | 7.79.1-150400.5.18.1 | 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.79.1-150400.5.18.1 | 7.79.1-150400.5.18.1 | 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.79.1-150400.5.18.1 | 7.79.1-150400.5.18.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.79.1-150400.5.18.1 | 7.79.1-150400.5.18.1 | 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.79.1-150400.5.18.1 | 7.79.1-150400.5.18.1 | 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.79.1-150400.5.15.1 | 7.79.1-150400.5.15.1 | 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-2023-23915 | — | < 7.79.1-150400.5.15.1 | 7.79.1-150400.5.15.1 | Feb 23, 2023 | A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality to behave incorrectly when multiple URLs are requested in parallel. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure | ||
| CVE-2023-23914 | — | < 7.79.1-150400.5.15.1 | 7.79.1-150400.5.15.1 | Feb 23, 2023 | A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality fail when multiple URLs are requested serially. Using its HSTS support, curl can be instructed to use HTTPS instead of usingan insecure clear-text HTTP step | ||
| CVE-2022-43552 | — | < 7.79.1-150400.5.12.1 | 7.79.1-150400.5.12.1 | 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-43551 | — | < 7.79.1-150400.5.12.1 | 7.79.1-150400.5.12.1 | Dec 23, 2022 | A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanis | ||
| CVE-2022-32221 | — | < 7.79.1-150400.5.9.1 | 7.79.1-150400.5.9.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 |
- affected < 8.0.1-150400.5.36.1fixed 8.0.1-150400.5.36.1
When saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use.
- affected < 8.0.1-150400.5.36.1fixed 8.0.1-150400.5.36.1
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 < 8.0.1-150400.5.32.1fixed 8.0.1-150400.5.32.1
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 < 8.0.1-150400.5.32.1fixed 8.0.1-150400.5.32.1
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-38039Sep 15, 2023affected < 8.0.1-150400.5.29.1fixed 8.0.1-150400.5.29.1
When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API. However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endles
- CVE-2023-28322May 26, 2023affected < 8.0.1-150400.5.23.1fixed 8.0.1-150400.5.23.1
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 < 8.0.1-150400.5.23.1fixed 8.0.1-150400.5.23.1
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-28320May 26, 2023affected < 8.0.1-150400.5.23.1fixed 8.0.1-150400.5.23.1
A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using `alarm()` an
- CVE-2023-28319May 26, 2023affected < 8.0.1-150400.5.23.1fixed 8.0.1-150400.5.23.1
A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now fre
- CVE-2023-27538Mar 30, 2023affected < 7.79.1-150400.5.18.1fixed 7.79.1-150400.5.18.1
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.79.1-150400.5.18.1fixed 7.79.1-150400.5.18.1
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.79.1-150400.5.18.1fixed 7.79.1-150400.5.18.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.79.1-150400.5.18.1fixed 7.79.1-150400.5.18.1
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.79.1-150400.5.18.1fixed 7.79.1-150400.5.18.1
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.79.1-150400.5.15.1fixed 7.79.1-150400.5.15.1
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-2023-23915Feb 23, 2023affected < 7.79.1-150400.5.15.1fixed 7.79.1-150400.5.15.1
A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality to behave incorrectly when multiple URLs are requested in parallel. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure
- CVE-2023-23914Feb 23, 2023affected < 7.79.1-150400.5.15.1fixed 7.79.1-150400.5.15.1
A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality fail when multiple URLs are requested serially. Using its HSTS support, curl can be instructed to use HTTPS instead of usingan insecure clear-text HTTP step
- CVE-2022-43552Feb 9, 2023affected < 7.79.1-150400.5.12.1fixed 7.79.1-150400.5.12.1
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-43551Dec 23, 2022affected < 7.79.1-150400.5.12.1fixed 7.79.1-150400.5.12.1
A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanis
- CVE-2022-32221Dec 5, 2022affected < 7.79.1-150400.5.9.1fixed 7.79.1-150400.5.9.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
Page 1 of 2