Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update: curl #1578

Open
dongsupark opened this issue Nov 7, 2024 · 0 comments
Open

update: curl #1578

dongsupark opened this issue Nov 7, 2024 · 0 comments
Labels
advisory security advisory security security concerns

Comments

@dongsupark
Copy link
Member

Name: curl
CVEs: CVE-2024-9681
CVSSs: n/a
Action Needed: update to >= 8.11.0

Summary: 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.

refmap.gentoo: https://bugs.gentoo.org/942952

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
advisory security advisory security security concerns
Projects
Development

No branches or pull requests

1 participant