Show filters
263 Total Results
Displaying 31-40 of 263
Sort by:
Attacker Value
Unknown
CVE-2023-3107
Disclosure Date: August 01, 2023 (last updated February 25, 2025)
A set of carefully crafted ipv6 packets can trigger an integer overflow in the calculation of a fragment reassembled packet's payload length field. This allows an attacker to trigger a kernel panic, resulting in a denial of service.
0
Attacker Value
Unknown
CVE-2023-38403
Disclosure Date: July 17, 2023 (last updated February 25, 2025)
iperf3 before 3.14 allows peers to cause an integer overflow and heap corruption via a crafted length field.
0
Attacker Value
Unknown
CVE-2023-2953
Disclosure Date: May 30, 2023 (last updated February 25, 2025)
A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.
0
Attacker Value
Unknown
CVE-2023-27538
Disclosure Date: March 30, 2023 (last updated February 24, 2025)
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 them for subsequent transfers if the configurations match. However, two SSH settings were omitted from the configuration check, allowing them to match easily, potentially leading to the reuse of an inappropriate connection.
0
Attacker Value
Unknown
CVE-2023-27537
Disclosure Date: March 30, 2023 (last updated February 24, 2025)
A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free.
0
Attacker Value
Unknown
CVE-2023-27536
Disclosure Date: March 30, 2023 (last updated February 24, 2025)
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 affects krb5/kerberos/negotiate/GSSAPI transfers and could potentially result in unauthorized access to sensitive information. The safest option is to not reuse connections if the CURLOPT_GSSAPI_DELEGATION option has been changed.
0
Attacker Value
Unknown
CVE-2023-27535
Disclosure Date: March 30, 2023 (last updated February 24, 2025)
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. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information.
0
Attacker Value
Unknown
CVE-2023-27533
Disclosure Date: March 30, 2023 (last updated February 24, 2025)
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 content or perform option negotiation without the application's intent. This vulnerability could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system.
0
Attacker Value
Unknown
CVE-2023-23916
Disclosure Date: February 23, 2023 (last updated February 24, 2025)
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 "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.
0
Attacker Value
Unknown
CVE-2023-23915
Disclosure Date: February 23, 2023 (last updated February 24, 2025)
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 clear-text HTTP step even when HTTP is provided in the URL. This HSTS mechanism would however surprisingly fail when multiple transfers are done in parallel as the HSTS cache file gets overwritten by the most recentlycompleted transfer. A later HTTP-only transfer to the earlier host name would then *not* get upgraded properly to HSTS.
0