Unknown
CVE-2024-9681
CVE ID
AttackerKB requires a CVE ID in order to pull vulnerability data and references from the CVE list and the National Vulnerability Database. If available, please supply below:
Add References:
Unknown
(0 users assessed)Unknown
(0 users assessed)Unknown
Unknown
Unknown
MITRE ATT&CK
Collection
Command and Control
Credential Access
Defense Evasion
Discovery
Execution
Exfiltration
Impact
Initial Access
Lateral Movement
Persistence
Privilege Escalation
Topic Tags
Description
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.
Add Assessment
No one has assessed this topic. Be the first to add your voice to the community.
CVSS V3 Severity and Metrics
General Information
Vendors
- curl
Products
- curl
References
Additional Info
Technical Analysis
Report as Emergent Threat Response
Report as Exploited in the Wild
CVE ID
AttackerKB requires a CVE ID in order to pull vulnerability data and references from the CVE list and the National Vulnerability Database. If available, please supply below: