CVE-2026-73479
Description
A flaw was found in dua-cli. This vulnerability allows attackers to craft malicious file names containing terminal escape sequences, specifically Operating System Command (OSC) or Control Sequence Introducer (CSI) sequences. When these marked file paths are printed after exiting the Text-based User Interface (TUI), the terminal emulator interprets these sequences. This can lead to consequences such as title spoofing or clipboard manipulation.
Statement
A terminal escape sequence injection flaw was found in dua-cli. When files are marked for deletion in the interactive TUI and the user exits, dua-cli prints the marked file paths to the terminal without neutralizing control characters, allowing an attacker who can place a file with a crafted name in a scanned directory to inject OSC/CSI escape sequences that the terminal emulator interprets (for example, window-title spoofing or clipboard manipulation). Red Hat rates this as Moderate: exploitation is local, requires the victim to run dua-cli interactively on attacker-influenced content and to mark the malicious file, and the impact is limited to the terminal emulator rather than the application or host. Red Hat Enterprise Linux does not ship dua-cli; the package is present only in Fedora and EPEL (rust-dua-cli), which are addressed through the community update process.
Mitigation
Avoid running dua-cli's interactive mode on directories containing files from untrusted sources, and do not mark files with suspicious names for deletion. This issue is resolved in dua-cli 2.42.0, which sanitizes control characters in printed marked paths.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability,Non-Repudiation
Technical Impact: Modify Application Data; Hide Activities; Execute Unauthorized Code or Commands
Interpretation of the log files may be hindered or misdirected if an attacker can supply data to the application that is subsequently logged verbatim. In the most benign case, an attacker may be able to insert false entries into the log file by providing the application with input that includes appropriate characters. Forged or otherwise corrupted log files can be used to cover an attacker's tracks, possibly by skewing statistics, or even to implicate another party in the commission of a malicious act. If the log file is processed automatically, the attacker can render the file unusable by corrupting the format of the file or injecting unexpected characters. An attacker may inject code or other commands into the log file and take advantage of a vulnerability in the log processing utility.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
