CVE-2024-24806

Description

A server-side request forgery (SSRF) flaw was found in the libuv package due to how the hostname_ascii variable is handled in uv_getaddrinfo and uv__idna_toascii. When the hostname exceeds 256 characters, it gets truncated without a terminating null byte. As a result, attackers may be able to access internal APIs or for websites that allow users to have username.example.com pages. Internal services that crawl or cache these user pages can be exposed to SSRF attacks if a malicious user chooses a long vulnerable username. This issue could allow an attacker to craft payloads that resolve to unintended IP addresses, bypassing developer checks.

Statement

The CVE-2024-24806 vulnerability in libuv, can be classified as a moderate severity issue rather than critical due to several mitigating factors. Firstly, the exploit requires specific conditions to be met, including the use of hostnames exceeding 256 characters, limiting its applicability. Additionally, the vulnerability primarily exposes servers to SSRF attacks and unauthorized access to internal APIs, rather than facilitating direct system compromise or data exfiltration. Furthermore, the exploit's detection and exploitation require a degree of sophistication, reducing the likelihood of widespread exploitation. While the potential impact on systems leveraging libuv is notable, prudent security measures, such as network controls and vigilant monitoring, can effectively mitigate the risk, thus warranting a moderate severity classification.

Mitigation

Mitigation for this issue is either not available or the currently available options don't 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).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.37.37.3
Attack VectorNetworkNetworkNetwork
Attack ComplexityLowLowLow
Privileges RequiredNoneNoneNone
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityLowLowLow
Integrity ImpactLowLowLow
Availability ImpactLowLowLow

Vector

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

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

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

Red Hat CVSS v3 Score Explanation

CVE-2024-24806 warrants a moderate severity rating of C:L/I:L/A:L in the Common Vulnerability Scoring System (CVSS). While the vulnerability exposes systems to server-side request forgery (SSRF) attacks and potential unauthorized access to internal APIs, its impact on confidentiality, integrity, and availability is limited. The likelihood of exploitation is reduced due to specific conditions required for the exploit, and the vulnerability does not directly compromise data integrity or cause service downtime.

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Application Data

Integrity

Technical Impact: Execute Unauthorized Code or Commands

Access Control

Technical Impact: Bypass Protection Mechanism

By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.

Frequently Asked Questions

Want to get errata notifications? Sign up here.