uutils coreutils vulnerabilities

A TOCTOU race condition exists in the mkfifo utility of uutils coreutils. A local attacker with write access to the parent directory can swap the newly created FIFO for a symbolic link, potentially leading to privilege escalation.

A logic error in the `ln` utility of uutils coreutils causes the program to reject source paths containing non-UTF-8 filename bytes when using target-directory forms (e.g., `ln SOURCE... DIRECTORY`). While GNU ln treats filenames as raw bytes and creates links correctly, the uutils implementation enforces UTF-8 encoding.

The 'id' utility in uutils coreutils miscalculates the 'groups=' section of its output. The implementation uses the user's real GID instead of their effective GID to compute the group list, leading to potentially divergent output compared to GNU coreutils.

A vulnerability in the rm utility of uutils coreutils allows bypassing safeguards that protect the current directory. The utility correctly refuses to delete . or .., but fails to recognize equivalent paths with trailing slashes, such as ./ or .///.

The touch utility in uutils coreutils is vulnerable to a TOCTOU race condition during file creation. After identifying a missing path, the utility later attempts creation using File::create(), which internally uses O_TRUNC. An attacker can exploit this window to create a file.

A Time-of-Check to Time-of-Use (TOCTOU) race condition exists in the mv utility of uutils coreutils during cross-device operations. The utility removes the destination path before recreating it through a copy operation, which a local attacker with write access to the destination directory can exploit.

The nohup utility in uutils coreutils creates its default output file, nohup.out, without specifying explicit restricted permissions. This causes the file to inherit umask-based permissions, typically resulting in a world-readable file (0644).

A TOCTOU vulnerability in the cp utility of uutils coreutils allows an attacker to bypass the intended no-dereference behavior. The utility checks if a source path is a symbolic link using path-based metadata but subsequently opens it without the O_NOFOLLOW flag.

The 'id' utility in uutils coreutils incorrectly displays data in 'pretty print' mode when the real UID differs from the effective UID. The implementation mistakenly uses the effective GID instead of the effective UID when looking up the name of the effective user, leading to misleading output.

The cp utility in uutils coreutils is vulnerable to an information disclosure race condition. Destination files are initially created with umask-derived permissions (e.g., 0644) before being restricted to their final mode (e.g., 0600) later in the process. A local attacker can race to open the file before the permission change.

A TOCTOU vulnerability in the split utility of uutils coreutils allows an attacker to replace the output file between the check and use, potentially leading to data loss. The flaw occurs because the program checks file identity based on paths but later opens the file without re-verification.

A Time-of-Check to Time-of-Use (TOCTOU) vulnerability exists in the mv utility of uutils coreutils during cross-device moves. The extended attribute (xattr) preservation logic uses multiple path-based system calls that perform fresh path-to-inode lookups for each operation. A local attacker with write access can exploit this race condition.

The mv utility in uutils coreutils fails to preserve file ownership during moves across different filesystem boundaries. It falls back to a copy-and-delete routine that creates the destination file using the caller's UID/GID instead of the source's metadata.

The cp utility in uutils coreutils fails to properly handle setuid and setgid bits when ownership preservation fails. When copying with the -p (preserve) flag, the utility applies the source mode bits even if the chown operation is unsuccessful. This can result in a user-owned copy retaining original setuid/setgid bits.

The sort utility in uutils coreutils crashes (panics) when using the --files0-from option with inputs containing non-UTF-8 filenames. The implementation enforces UTF-8 encoding and uses expect(), causing an immediate crash upon encountering valid but non-UTF-8 paths.

A vulnerability in the tail utility of uutils coreutils allows exfiltration of sensitive file contents when using the --follow=name option. Unlike GNU tail, the uutils implementation continues to monitor a path after it has been replaced by a symbolic link, subsequently outputting its contents.

The dd utility in uutils coreutils suppresses errors during file truncation operations by unconditionally calling Result::ok() on truncation attempts. While intended to mimic GNU behavior for special files like /dev/null, the uutils implementation also hides failures on regular files and directories.

A logic error in the env utility of uutils coreutils causes incorrect parsing of command-line arguments when using the -S (split-string) option. Unlike GNU env, the uutils implementation mishandles backslashes within single quotes, leading to incompatibility.

uutils coreutils before version 0.10.0 apply setuid or setgid mode to install destinations before finalizing ownership changes, allowing privileged users to leave setuid executables owned by the privileged invoker when ownership changes fail. Attackers can execute leftover setuid files with elevated privileges when ownership change operations fail on capability-restricted systems.