CVE Vulnerability Catalog

A logging issue in iOS and iPadOS caused notifications marked for deletion to be unexpectedly retained on the device. Apple addressed this with improved data redaction in iOS 15.8.8, 16.7.16, 18.7.8, 26.4.2 and iPadOS 15.8.8, 16.7.16, 17.7.11, 18.7.8 and 26.4.2.

A logic error in the cut utility of uutils coreutils causes the program to incorrectly interpret the literal two-byte string '' (two single quotes) as an empty delimiter. The implementation mistakenly maps this string to the NUL character for both the -d and --output-delimiter options. This can lead to silent data corruption or logic errors in automated scripts and data pipelines.

A Time-of-Check to Time-of-Use (TOCTOU) vulnerability exists in the chcon utility of uutils coreutils during recursive operations. The implementation resolves recursive targets using a fresh path lookup (via fts_accpath) rather than binding traversal and label application to the directory state encountered during traversal; because operations are not anchored to file descriptors, a local attacker with write access to a directory tree can exploit timing-sensitive rename or symlink races to redirect a privileged recursive relabeling operation to unintended files or directories. This breaks SELinux administration hardening expectations and can lead to unauthorized modification of security labels on sensitive system objects.

A Time-of-Check to Time-of-Use (TOCTOU) vulnerability exists in the split utility of uutils coreutils. The program checks identity between input and output files using their paths before initiating the split operation, but subsequently opens the output file with truncation after this path-based validation. A local attacker with write access to the directory can exploit this race window by manipulating mutable path components (e.g., swapping a path with a symbolic link), causing split to truncate and write to an unintended target file, potentially including the input file itself or other sensitive files accessible to the process, leading to permanent data loss.

A logic error in the ln utility of uutils coreutils causes it to dereference a symbolic link target even when --no-dereference (or -n) is explicitly provided. The implementation only honored the no-dereference intent when --force was also enabled. This flaw causes ln to follow a symlink pointing to a directory and create new links inside that target directory instead of treating the symlink itself as the destination. In environments where a privileged user or system script uses ln -n to update a symlink, a local attacker could manipulate existing symlinks to redirect file creation into sensitive directories.

The id utility in uutils coreutils miscalculates the groups= section of its output by using a user's real GID instead of their effective GID to compute the group list. This can diverge from GNU coreutils, and because many scripts and automated processes rely on id output for security-critical access-control or permission decisions, the discrepancy can lead to unauthorized access or security misconfigurations.

An argument parsing error in the kill utility of uutils coreutils incorrectly interprets kill -1 as a request to send the default signal (SIGTERM) to PID -1. Sending a signal to PID -1 causes the kernel to terminate all processes visible to the caller, potentially leading to a system crash or massive process termination.

The printenv utility in uutils coreutils fails to display environment variables containing invalid UTF-8 byte sequences. The implementation silently skips these entries rather than printing raw bytes, allowing malicious environment variables (e.g., adversarial LD_PRELOAD values) to evade inspection.

The mv utility in uutils coreutils improperly handles directory trees containing symbolic links during moves across filesystem boundaries. Instead of preserving symlinks, the implementation expands them, copying the linked targets as real files or directories at the destination. This can lead to resource exhaustion, unexpected duplication of sensitive data, or infinite recursion with symlink loops.

A TOCTOU race condition exists in the mv utility of uutils coreutils during cross-device operations. The utility removes the destination path before recreating it, allowing a local attacker with write access to substitute a symlink and overwrite an arbitrary target file.

The rm utility in uutils coreutils allows bypass of safeguards protecting the current directory. While it correctly refuses to delete . or .., it fails to recognize equivalent paths with trailing slashes (e.g., ./ or .///), so executing rm -rf ./ silently recursively deletes all contents of the current directory.

The touch utility in uutils coreutils is vulnerable to a Time-of-Check to Time-of-Use (TOCTOU) race condition during file creation. When the utility identifies a missing path, it later attempts creation using File::create(), which internally uses O_TRUNC. An attacker can exploit this window to create a file or swap a symlink at the target path, causing touch to truncate an existing file and leading to permanent data loss.

A Time-of-Check to Time-of-Use (TOCTOU) vulnerability in the cp utility of uutils coreutils allows an attacker to bypass no-dereference intent. The utility checks if a source path is a symbolic link using path-based metadata but subsequently opens it without the O_NOFOLLOW flag. An attacker with concurrent write access can swap a regular file for a symbolic link during this window, causing a privileged cp process to copy the contents of arbitrary sensitive files into a destination controlled by the attacker.

The cp utility in uutils coreutils, when performing recursive copies (-R), incorrectly treats character and block device nodes as stream sources rather than preserving them. Because the implementation reads bytes into regular files at the destination instead of using mknod, device semantics are destroyed (e.g., /dev/null becomes a regular file), which can lead to runtime denial of service through disk exhaustion or process hangs when reading from unbounded device nodes.

The cp utility in uutils coreutils is vulnerable to an information disclosure race condition. Destination files are created with umask-derived permissions before being restricted to their final mode, allowing a local attacker to race and open the file.

A Time-of-Check to Time-of-Use (TOCTOU) vulnerability exists in the install utility of uutils coreutils when using the -D flag. The command creates parent directories and then performs a second path resolution to create the target file, neither anchored to a directory file descriptor. An attacker with concurrent write access can replace a path component with a symbolic link between these operations, redirecting the privileged write to an arbitrary file system location.

The install utility in uutils coreutils is vulnerable to a Time-of-Check to Time-of-Use (TOCTOU) race condition during file installation. It unlinks an existing destination file and recreates it without the O_EXCL flag, allowing a local attacker to swap the path with a symbolic link and redirect privileged writes to overwrite arbitrary system files.

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 to the directory can exploit this race to swap files between calls, causing the destination file to receive an inconsistent mix of security xattrs, such as SELinux labels or file capabilities.

The mv utility in uutils coreutils fails to preserve file ownership during moves across different filesystem boundaries. The utility falls back to a copy-and-delete routine that creates the destination file using the caller's UID/GID rather than the source's metadata. This breaks backups and migrations, causing files moved by a privileged user (e.g., root) to become root-owned unexpectedly, which can lead to information disclosure or restricted access for the intended owners.

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 privileged bits, creating unexpected privileged executables that violate local security policies. This differs from GNU cp, which clears these bits when ownership cannot be preserved.