suse/curl&distro=SUSE Linux Enterprise Micro 5.1

Vulnerabilities (32)

• CVE-2025-9086HigSep 12, 2025
  affected < 8.14.1-150200.4.91.1fixed 8.14.1-150200.4.91.1

  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-2025-10148Sep 12, 2025
  affected < 8.14.1-150200.4.91.1fixed 8.14.1-150200.4.91.1

  curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection. A predictable mask pattern allows for a malicious server to induce traf

• CVE-2025-0725Feb 5, 2025
  affected < 7.66.0-150200.4.84.1fixed 7.66.0-150200.4.84.1

  When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the `CURLOPT_ACCEPT_ENCODING` option, **using zlib 1.2.0.3 or older**, an attacker-controlled integer overflow would make libcurl perform a buffer overflow.

• CVE-2025-0167Feb 5, 2025
  affected < 7.66.0-150200.4.84.1fixed 7.66.0-150200.4.84.1

  When asked to use a `.netrc` file for credentials **and** to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has a `default` entry that omits both l

• CVE-2024-11053Dec 11, 2024
  affected < 7.66.0-150200.4.81.1fixed 7.66.0-150200.4.81.1

  When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has an entry that matches the redirect

• CVE-2024-8096Sep 11, 2024
  affected < 7.66.0-150200.4.78.1fixed 7.66.0-150200.4.78.1

  When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead wrongly consider the response as fine. If the returned status reports

• CVE-2024-7264Jul 31, 2024
  affected < 7.66.0-150200.4.75.1fixed 7.66.0-150200.4.75.1

  libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an ASN.1 Generalized Time field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the *time fraction*, leading to a `strlen()` getting performed on a pointer t

• CVE-2024-2398Mar 27, 2024
  affected < 7.66.0-150200.4.69.1fixed 7.66.0-150200.4.69.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

• CVE-2024-2004Mar 27, 2024
  affected < 7.66.0-150200.4.69.1fixed 7.66.0-150200.4.69.1

  When a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protoc

• CVE-2023-46218MedDec 7, 2023
  affected < 7.66.0-150200.4.63.1fixed 7.66.0-150200.4.63.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

• CVE-2023-38546LowOct 18, 2023
  affected < 7.66.0-150200.4.60.1fixed 7.66.0-150200.4.60.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

• CVE-2023-28322May 26, 2023
  affected < 7.66.0-150200.4.57.1fixed 7.66.0-150200.4.57.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, 2023
  affected < 7.66.0-150200.4.57.1fixed 7.66.0-150200.4.57.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, 2023
  affected < 7.66.0-150200.4.57.1fixed 7.66.0-150200.4.57.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-27538Mar 30, 2023
  affected < 7.66.0-150200.4.52.1fixed 7.66.0-150200.4.52.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, 2023
  affected < 7.66.0-150200.4.52.1fixed 7.66.0-150200.4.52.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, 2023
  affected < 7.66.0-150200.4.52.1fixed 7.66.0-150200.4.52.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, 2023
  affected < 7.66.0-150200.4.52.1fixed 7.66.0-150200.4.52.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, 2023
  affected < 7.66.0-150200.4.52.1fixed 7.66.0-150200.4.52.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, 2023
  affected < 7.66.0-150200.4.52.1fixed 7.66.0-150200.4.52.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