Cloudanix VulnDB

CVE-2024-56433

Low · 3.6

CVSS

3.6

EPSS

0.4%

Published

Dec 26, 2024

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A default setting for mapping extra user IDs can accidentally give one person access to another person's files when computers share a network, and updating the software plus checking the settings fixes it.

Exploitation
Local Privilege
Attacker needs
Low Privilege
Complexity
High
Impact
Privilege Gain
Component
Application
Class
Misconfiguration
Remediation
Config Change
Effort
Low
Patch risk
Low

What it actually does

Default subuid range allocation in shadow-utils (uid 100000-165535) can overlap with UIDs assigned on locally administered networks, allowing newuidmap to grant unintended access to files owned by those UIDs on NFS mounts or local resources.

Why it matters to the business

Organizations using shadow for user namespace mapping risk unauthorized access to shared storage or home directories when network-assigned UIDs collide with the default subuid range, potentially exposing sensitive data without requiring elevated privileges.

How an attack unfolds

An attacker with a UID matching the default subuid range logs in (remotely or locally), invokes newuidmap to map into the overlapping range, and gains read/write access to files owned by that UID on NFS home directories or equivalent resources.

How to fix it

Upgrade shadow-maint/shadow to commit 68061f2059124f5aa450dfbf6bbad3e7a6f65f9f or later; on Ubuntu 18.04 LTS upgrade ikiwiki to 3.20180228-1 or later. Manually adjust /etc/subuid ranges to avoid overlap with any locally administered network UID space and verify mappings after changes.

How to confirm the fix worked

Confirm package versions match or exceed the listed fixed releases, inspect /etc/subuid for non-overlapping ranges, and test newuidmap behavior with sample accounts whose UIDs sit near network-assigned values.

Typical attack path

  1. Identify or control a user account whose UID falls inside the 100000-165535 subuid range
  2. Trigger login or session that invokes newuidmap or subordinate UID mapping
  3. Access NFS-mounted home directories or same-host resources belonging to the colliding UID
  4. Read, modify, or exfiltrate data that should have been protected by UID separation

How to detect it

Review authentication and mapping logs for unexpected newuidmap invocations or UID mappings that align with the default 100000-165535 range; examine NFS access patterns for users whose UIDs fall inside that range.

What your security team should do

  • Prioritize upgrade of shadow-utils on all systems using user namespaces or NFS home directories
  • Audit existing /etc/subuid and /etc/subgid files for overlap with any known network UID ranges
  • Document and enforce a site-wide policy for subuid allocation that excludes local network UID blocks
  • Monitor EPSS trend and re-evaluate if exploit maturity increases

The record

shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.

Affected packages

Ecosystem Package Introduced Fixed
AlmaLinux:10 shadow-utils 0 2:4.15.0-8.el10
AlmaLinux:10 shadow-utils-subid 0 2:4.15.0-8.el10
AlmaLinux:10 shadow-utils-subid-devel 0 2:4.15.0-8.el10
AlmaLinux:9 shadow-utils 0 2:4.9-15.el9
AlmaLinux:9 shadow-utils-subid 0 2:4.9-15.el9
AlmaLinux:9 shadow-utils-subid-devel 0 2:4.9-15.el9
Chainguard just-newuidmap-newgidmap 0 0
Chainguard shadow 0 0
Chainguard shadow-conv 0 0
Chainguard shadow-dev 0 0
Chainguard shadow-doc 0 0
Chainguard shadow-login 0 0
Chainguard shadow-subids 0 0
Debian:11 shadow 0 No fix
Debian:12 shadow 0 No fix
Debian:13 shadow 0 No fix
Debian:14 shadow 0 No fix
Ubuntu:20.04:LTS shadow 0 No fix
Ubuntu:22.04:LTS shadow 0 No fix
Ubuntu:24.04:LTS shadow 0 No fix
Ubuntu:24.10 shadow 0 No fix
Ubuntu:25.04 shadow 0 No fix
Ubuntu:25.10 shadow 0 No fix
Ubuntu:Pro:14.04:LTS shadow 0 No fix
Ubuntu:Pro:16.04:LTS shadow 0 No fix
Ubuntu:Pro:18.04:LTS shadow 0 No fix
Ubuntu:Pro:20.04:LTS shadow 0 No fix
Wolfi just-newuidmap-newgidmap 0 0
Wolfi shadow 0 0
Wolfi shadow-conv 0 0
Wolfi shadow-dev 0 0
Wolfi shadow-doc 0 0
Wolfi shadow-login 0 0
Wolfi shadow-subids 0 0

Related vulnerabilities