CVE-2000-0076 in nvi
Summary
by MITRE
nviboot boot script in the Debian nvi package allows local users to delete files via malformed entries in vi.recover.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 04/20/2026
The vulnerability described in CVE-2000-0076 resides within the Debian nvi package's nviboot boot script which handles the initialization and recovery process for the nvi text editor. This flaw represents a classic privilege escalation and file deletion vulnerability that emerged from improper input validation within the recovery mechanism of the editor. The issue specifically manifests when the vi.recover configuration file contains malformed entries that the nviboot script fails to properly sanitize or validate before processing. When a local user manipulates these entries, the script executes destructive operations that can result in unauthorized file deletion from the system.
The technical root cause of this vulnerability stems from inadequate parameter validation and sanitization within the nviboot script's handling of recovery file entries. The vi.recover file typically contains information about previously edited files that need recovery, but when malformed entries are introduced, the script's parsing logic fails to properly restrict the operations that can be performed. This vulnerability falls under CWE-20, which describes improper input validation, and CWE-77, which addresses command injection vulnerabilities. The script essentially treats user-supplied input as executable commands without proper validation, creating a dangerous execution path that allows local users to manipulate the system's file structure.
The operational impact of this vulnerability is significant for systems running the affected Debian nvi package, as it enables local users to perform unauthorized file deletion operations that could compromise system integrity and data availability. Attackers can exploit this weakness by creating malicious entries in the vi.recover file that, when processed by the nviboot script, trigger file deletion commands. This creates a persistent threat vector that can be leveraged to remove critical system files, configuration data, or user documents. The vulnerability is particularly concerning because it operates at the local user level, meaning any user with access to the system can potentially exploit it without requiring elevated privileges, though the actual impact depends on the permissions of the user running the nvi editor.
From a cybersecurity perspective, this vulnerability demonstrates the importance of proper input validation and the principle of least privilege in system design. The ATT&CK framework categorizes this type of vulnerability under privilege escalation techniques, specifically targeting the execution of malicious commands through compromised system utilities. Organizations should implement strict file permissions and monitoring for the vi.recover file to prevent unauthorized modifications. The recommended mitigations include applying the vendor patch that properly validates input entries, restricting write permissions to the vi.recover file, and implementing regular system audits to detect unauthorized modifications. Additionally, system administrators should consider disabling the recovery feature entirely if it's not required, or implementing more robust input sanitization mechanisms that prevent the execution of potentially dangerous commands from user-controlled input sources.