domain-scoped PSL domain cookie
curl
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
8.21.08.20.08.19.08.18.08.17.08.16.0| No fix yet |
When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a `Set-Cookie` header where the `Domain` attribute explicitly matches an origin host that is itself a public suffix (e.g., `Domain=co.uk` set by `co.uk`).
Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope (`.co.uk`). Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., `attacker.co.uk`).
From the CVE record · curl
With libpsl support enabled, libcurl can give a cookie wildcard scope when a Set-Cookie Domain matches an origin host that is itself a public suffix. A server returning that header can cause the cookie to be sent in later requests or HTTP redirects to sibling subdomains, including an attacker-controlled subdomain. The input does not specify authentication or user-interaction requirements.
Anyone running curl or software using libcurl with libpsl support enabled should check their version; affected versions are not specified.