Security update for curl SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2025:20083-1 Final 1 1 2025-02-03T09:07:41Z current 2025-02-03T09:07:41Z 2025-02-03T09:07:41Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for curl This update for curl fixes the following issues: - CVE-2024-9681: Fixed HSTS subdomain overwrites parent cache entry (bsc#1232528) The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-SLE-Micro-6.0-138 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2025/suse-su-202520083-1/ Link for SUSE-SU-2025:20083-1 https://lists.suse.com/pipermail/sle-security-updates/2025-June/021232.html E-Mail link for SUSE-SU-2025:20083-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1232528 SUSE Bug 1232528 https://www.suse.com/security/cve/CVE-2024-9681/ SUSE CVE CVE-2024-9681 page SUSE Linux Micro 6.0 curl-8.6.0-4.1 libcurl4-8.6.0-4.1 curl-8.6.0-4.1 as a component of SUSE Linux Micro 6.0 libcurl4-8.6.0-4.1 as a component of SUSE Linux Micro 6.0 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. CVE-2024-9681 SUSE Linux Micro 6.0:curl-8.6.0-4.1 SUSE Linux Micro 6.0:libcurl4-8.6.0-4.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520083-1/ https://www.suse.com/security/cve/CVE-2024-9681.html CVE-2024-9681 https://bugzilla.suse.com/1232528 SUSE Bug 1232528