From: glsamaker@gentoo.org
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202501-05 ] libuv: Hostname Truncation
Date: Thu, 23 Jan 2025 06:17:02 -0000 [thread overview]
Message-ID: <173761302317.7.4214306805984072185@3f85d36892cf> (raw)
[-- Attachment #1: Type: text/plain, Size: 2502 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 202501-05
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: libuv: Hostname Truncation
Date: January 23, 2025
Bugs: #924127
ID: 202501-05
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability has been discovered in libuv, where hostname truncation
can lead to attacker-controlled lookups.
Background
==========
libuv is a multi-platform support library with a focus on asynchronous
I/O.
Affected packages
=================
Package Vulnerable Unaffected
-------------- ------------ ------------
dev-libs/libuv < 1.48.0 >= 1.48.0
Description
===========
Multiple vulnerabilities have been discovered in libuv. Please review
the CVE identifiers referenced below for details.
Impact
======
The uv_getaddrinfo function in src/unix/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.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All libuv users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-libs/libuv-1.48.0"
References
==========
[ 1 ] CVE-2024-24806
https://nvd.nist.gov/vuln/detail/CVE-2024-24806
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202501-05
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.
License
=======
Copyright 2025 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
https://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2025-01-23 6:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=173761302317.7.4214306805984072185@3f85d36892cf \
--to=glsamaker@gentoo.org \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox