VulnerableCode Package Details - pkg:generic/curl.se/curl@8.10.0

Search for packages

Vulnerability	Summary	Fixed by
VCID-83qm-twsu-k3hm Aliases: CVE-2025-4947	libcurl accidentally skips the certificate verification for QUIC connections when connecting to a host specified as an IP address in the URL. Therefore, it does not detect impostors or man-in-the-middle attacks.	8.14.0 Affected by 1 other vulnerability. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }}
VCID-97mb-c19v-bqcx Aliases: CVE-2025-0725	libcurl: Buffer Overflow in libcurl via zlib Integer Overflow	8.12.0 Affected by 2 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-gw9j-gggs-t7at Aliases: CVE-2024-11053	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 target hostname but the entry either omits just the password or omits both login and password.	8.11.1 Affected by 5 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-jxju-r4ej-ffev Aliases: CVE-2024-9681	When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout bleed over and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry earlier, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.	8.11.0 Affected by 5 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-t6fs-2jn9-bfbg Aliases: CVE-2025-0167	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 login and password. A rare circumstance.	8.12.0 Affected by 2 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-yfzf-g3sh-ubf5 Aliases: CVE-2025-5025	libcurl supports pinning of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.	8.14.0 Affected by 1 other vulnerability. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }}

Vulnerability

Summary

Fixed by

VCID-83qm-twsu-k3hm
Aliases:
CVE-2025-4947

libcurl accidentally skips the certificate verification for QUIC connections when connecting to a host specified as an IP address in the URL. Therefore, it does not detect impostors or man-in-the-middle attacks.

8.14.0
Affected by 1 other vulnerability.

VCID-97mb-c19v-bqcx
Aliases:
CVE-2025-0725

libcurl: Buffer Overflow in libcurl via zlib Integer Overflow

8.12.0
Affected by 2 other vulnerabilities.

VCID-gw9j-gggs-t7at
Aliases:
CVE-2024-11053

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 target hostname but the entry either omits just the password or omits both login and password.

8.11.1
Affected by 5 other vulnerabilities.

VCID-jxju-r4ej-ffev
Aliases:
CVE-2024-9681

When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.

8.11.0
Affected by 5 other vulnerabilities.

VCID-t6fs-2jn9-bfbg
Aliases:
CVE-2025-0167

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 login and password. A rare circumstance.

8.12.0
Affected by 2 other vulnerabilities.

VCID-yfzf-g3sh-ubf5
Aliases:
CVE-2025-5025

libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.

8.14.0
Affected by 1 other vulnerability.

Vulnerability	Summary	Aliases
VCID-w4x7-57vc-7yh7	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 another error than 'revoked' (like for example 'unauthorized') it is not treated as a bad certficate.	CVE-2024-8096

Vulnerability

Summary

Aliases

VCID-w4x7-57vc-7yh7

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 another error than 'revoked' (like for example 'unauthorized') it is not treated as a bad certficate.

CVE-2024-8096

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2025-05-28T20:09:44.944480+00:00	Curl Importer	Affected by	VCID-83qm-twsu-k3hm	https://curl.se/docs/CVE-2025-4947.json	36.0.0
2025-05-28T20:09:44.897297+00:00	Curl Importer	Affected by	VCID-yfzf-g3sh-ubf5	https://curl.se/docs/CVE-2025-5025.json	36.0.0
2025-03-28T13:43:16.649881+00:00	Curl Importer	Affected by	VCID-t6fs-2jn9-bfbg	https://curl.se/docs/CVE-2025-0167.json	36.0.0
2025-03-28T13:43:16.364803+00:00	Curl Importer	Affected by	VCID-97mb-c19v-bqcx	https://curl.se/docs/CVE-2025-0725.json	36.0.0
2025-01-16T20:10:06.488476+00:00	Curl Importer	Affected by	VCID-gw9j-gggs-t7at	https://curl.se/docs/CVE-2024-11053.json	35.1.0
2024-12-11T08:35:48.031810+00:00	Curl Importer	Affected by	VCID-gw9j-gggs-t7at	https://curl.se/docs/CVE-2024-11053.json	35.0.0
2024-11-19T00:55:33.692068+00:00	Curl Importer	Affected by	VCID-jxju-r4ej-ffev	https://curl.se/docs/CVE-2024-9681.json	34.3.2
2024-09-18T09:28:38.188524+00:00	Curl Importer	Fixing	VCID-w4x7-57vc-7yh7	https://curl.se/docs/CVE-2024-8096.json	34.0.1