CVE-2024-9681

mediumpriority · track · 27EPSS 0.020 · 80 %ileDEEUNLRUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
1.99% (80th) EPSS
CVSS 6.5 · medium
Is it mine?
221 products
Check your exposure
Who says so?
9 sources
cnnvd · enisa_euvd · fstec_bdu · cert_bund

EPSS · scored 2026-10-22

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.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

02

cvss

Technical severity, 0–10. One row per scoring source.

6.5
010

base score 0–10 · higher = more severe · hover a vector to decode

v3.16.5mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Lprimary · NVD / NIST USexploitability 2.2 · impact 4.2
v3.16.5mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Lsecondary · CISA US
v3.15.9mediumAV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondary · FSTEC (BDU) RU
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondary · ENISA EU
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Nsecondaryexploitability 2.2 · impact 3.6
v3.16.5mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Lsecondary · Siemens ProductCERT DE
v3.16.5mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Lsecondary · Phoenix Contact PSIRT DE
v3.16mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L/E:Usecondary · CVSS-BT (t0sche)
v3.16.5mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:Lsecondary · NCSC-NL NL
03

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
04

weaknesses

The CWE weakness classes this flaw belongs to.

05

affected products (221)

Products and version ranges known to be affected.

06

advisories (11)

Vendor and ecosystem advisories describing this.

  • NCSC-2025-0102Kwetsbaarheden verholpen in Apple macOSNL2025-04-01csaf · ncsc_nlNL

    Apple heeft meerdere kwetsbaarheden verholpen in macOS (Specifiek voor Ventura 13.7.5, Sequoia 15.4 en Sonoma 14.7.5).

  • NCSC-2025-0103Kwetsbaarheden verholpen in Apple iOS en iPadOSNL2025-04-01csaf · ncsc_nlNL

    Apple heeft meerdere kwetsbaarheden verholpen in iOS en iPadOS.

  • SSA-089022SSA-089022: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.32026-01-28csaf · siemens_psirtDE

    SINEC OS before V3.3 contains third-party components with multiple vulnerabilities. Siemens has released new versions for the affected products and recommends to update to the latest versions.

  • SSA-355557SSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.22025-08-12csaf · siemens_psirtDE

    SINEC OS before V3.2 contains third-party components with multiple vulnerabilities. Siemens has released new versions for the affected products and recommends to update to the latest versions.

  • VDE-2025-053Phoenix Contact: Multiple Vulnerabilities in PLCnext Firmware2025-07-08csaf · phoenix_contact_psirtDE

    Multiple Linux component vulnerabilities fixed in latest PLCnext Firmware release 2025.0.2

  • WID-SEC-W-2024-3342cURL: Schwachstelle ermöglicht Denial of ServiceDeutsch2024-11-05csaf · cert_bundDE

    Ein Angreifer kann eine Schwachstelle in cURL ausnutzen, um einen Denial of Service Angriff durchzuführen.

  • WID-SEC-W-2025-0663Apple iOS und iPadOS: Mehrere SchwachstellenDeutsch2025-03-31csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Apple iOS und Apple iPadOS ausnutzen, um vertrauliche Informationen preiszugeben, beliebigen Code auszuführen, einen Denial-of-Service-Zustand herbeizuführen, Sicherheitsmaßnahmen zu umgehen, erhöhte Rechte zu erlangen oder Daten zu manipulieren.

  • WID-SEC-W-2025-0668Apple macOS: Mehrere SchwachstellenDeutsch2025-03-31csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Apple macOS ausnutzen, um erhöhte Rechte - sogar Root-Rechte - zu erlangen, um vertrauliche Informationen offenzulegen, um beliebigen Code auszuführen, um Daten zu manipulieren, um Sicherheitsmaßnahmen - sogar Sandbox-Einschränkungen - zu umgehen oder um einen Denial-of-Service-Zustand auszulösen.

  • ICSA-25-226-07Siemens Third-Party Components in SINEC OS2025-08-12icsa · cisa_csaf_otUS

    SINEC OS before V3.2 contains third-party components with multiple vulnerabilities. Siemens has released new versions for the affected products and recommends to update to the latest versions.

  • ICSA-26-043-06Siemens SINEC OS2026-01-28icsa · cisa_csaf_otUS

    SINEC OS before V3.3 contains third-party components with multiple vulnerabilities. Siemens has released new versions for the affected products and recommends to update to the latest versions.

  • CURL-CVE-2024-9681HSTS subdomain overwrites parent cache entry2024-11-06vendor · osvUS

    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.

07

also known as (4)

Other names and identifiers for this entity.

08

sources

Which sources assert this record, and when.

10

references (21)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan