Server-Side Request Forgery (SSRF) Affecting nodejs18-devel package, versions <18.19.1-150400.9.18.2


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.11% (46th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-SLES155-NODEJS18DEVEL-6346951
  • published1 Mar 2024
  • disclosed29 Feb 2024

Introduced: 29 Feb 2024

CVE-2024-24806  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade SLES:15.5 nodejs18-devel to version 18.19.1-150400.9.18.2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs18-devel package and not the nodejs18-devel package as distributed by SLES. See How to fix? for SLES:15.5 relevant fixed versions and status.

libuv is a multi-platform support library with a focus on asynchronous I/O. The uv_getaddrinfo function in src/unix/getaddrinfo.c (and its windows counterpart src/win/getaddrinfo.c), truncates hostnames to 256 characters before calling getaddrinfo. This behavior can be exploited to create addresses like 0x00007f000001, which are considered valid by getaddrinfo and could allow an attacker to craft payloads that resolve to unintended IP addresses, bypassing developer checks. The vulnerability arises due to how the hostname_ascii variable (with a length of 256 bytes) is handled in uv_getaddrinfo and subsequently in 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 (similar to MySpace) that allows 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 has been addressed in release version 1.48.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

CVSS Scores

version 3.1