FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-11-19 19:12:13 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

These are the vulnerabilities relating to the commit you have selected:

VuXML ID	Description
02e33cd1-c655-11ee-8613-08002784c58d	curl -- OCSP verification bypass with TLS session reuse Hiroki Kurosawa reports: curl inadvertently kept the SSL session ID for connections in its cache even when the verify status (OCSP stapling) test failed. A subsequent transfer to the same hostname could then succeed if the session ID cache was still fresh, which then skipped the verify status check. Discovery 2024-01-31 Entry 2024-02-28 curl < 8.6.0 CVE-2024-0853 https://curl.se/docs/CVE-2024-0853.html
d6c19e8c-6806-11ee-9464-b42e991fc52e	curl -- SOCKS5 heap buffer overflow The curl team reports: This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the hostname to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that hostname can be is 255 bytes. If the hostname is detected to be longer than 255 bytes, curl switches to local name resolving and instead passes on the resolved address only to the proxy. Due to a bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long hostname to the target buffer instead of copying just the resolved address there. Discovery 2023-09-30 Entry 2023-10-11 Modified 2023-10-11 curl > 7.69.0 lt 8.4.0 cmake-core < 3.27.8 CVE-2023-38545 https://curl.se/docs/CVE-2023-38545.html

VuXML ID

Description

02e33cd1-c655-11ee-8613-08002784c58d

curl -- OCSP verification bypass with TLS session reuse

Hiroki Kurosawa reports:

curl inadvertently kept the SSL session ID for connections in its cache even when the verify status (OCSP stapling) test failed. A subsequent transfer to the same hostname could then succeed if the session ID cache was still fresh, which then skipped the verify status check.

Discovery 2024-01-31
Entry 2024-02-28
curl

< 8.6.0

CVE-2024-0853
https://curl.se/docs/CVE-2024-0853.html

d6c19e8c-6806-11ee-9464-b42e991fc52e

curl -- SOCKS5 heap buffer overflow

The curl team reports:

This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the hostname to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that hostname can be is 255 bytes. If the hostname is detected to be longer than 255 bytes, curl switches to local name resolving and instead passes on the resolved address only to the proxy. Due to a bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long hostname to the target buffer instead of copying just the resolved address there.

Discovery 2023-09-30
Entry 2023-10-11
Modified 2023-10-11
curl

> 7.69.0 lt 8.4.0

cmake-core

< 3.27.8

CVE-2023-38545
https://curl.se/docs/CVE-2023-38545.html