CVE-2024-9681

Description

A vulnerability was found in curl. 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 intended.

Statement

This flaw has been classified with a low severity primarily because it requires user interaction and a connection to a malicious subdomain. Additionally, this issue is only triggered when an HSTS cache file is being used with specific configurations when connecting to a malicious subdomain. This feature is enabled via the '--hsts' command line option. Furthermore, this issue will only cause parent domains that support HSTS for a short period of time and want to revert to HTTP to become inaccessible.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score3.96.55.9
Attack VectorLocalNetworkNetwork
Attack ComplexityLowHighHigh
Privileges RequiredLowNoneNone
User InteractionRequiredNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneNone
Integrity ImpactLowHighHigh
Availability ImpactLowLowNone

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L

NVD: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L

cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Understanding the Weakness (CWE)

Other

Technical Impact: Varies by Context

This can lead to incorrect results and resultant weaknesses. For example, the code might inadvertently compare references to objects, instead of the relevant contents of those objects, causing two "equal" objects to be considered unequal.

Frequently Asked Questions

Want to get errata notifications? Sign up here.