Skip to main content

CVE-2000-0219: Red Hat 6.0 allows local users to gain root access by booting single user and hitting ^C at the pass

High
VulnerabilityCVE-2000-0219cve-2000-0219cwe-264
Published: Wed Feb 23 2000 (02/23/2000, 05:00:00 UTC)
Source: NVD
Vendor/Project: redhat
Product: linux

Description

Red Hat 6.0 allows local users to gain root access by booting single user and hitting ^C at the password prompt.

AI-Powered Analysis

AILast updated: 06/25/2025, 11:45:21 UTC

Technical Analysis

CVE-2000-0219 is a local privilege escalation vulnerability affecting Red Hat Linux version 6.0. The vulnerability arises from the way the system handles booting into single-user mode. Specifically, when a system is booted into single-user mode, it typically prompts for the root password to prevent unauthorized access. However, in Red Hat 6.0, an attacker with local access can bypass this password prompt by pressing the interrupt key combination (^C) at the password prompt during the single-user boot process. This action effectively allows the attacker to gain root-level access without authentication. The vulnerability is rooted in improper access control (CWE-264), where the system fails to enforce authentication during a critical system state transition. Exploiting this vulnerability requires local access to the machine and physical or console access to reboot the system. Once exploited, the attacker gains full control over the system, including the ability to read, modify, or delete any data, install malicious software, or disrupt system availability. The CVSS v2 score of 7.2 reflects a high severity, with local attack vector, low attack complexity, no authentication required, and complete impact on confidentiality, integrity, and availability. No patch is available for this vulnerability, likely due to the age of the affected system version. There are no known exploits in the wild, but the simplicity of the bypass means that any attacker with local access and reboot capability can exploit it easily. This vulnerability primarily affects legacy systems still running Red Hat 6.0, which is an outdated Linux distribution released around 1999-2000.

Potential Impact

For European organizations, the impact of this vulnerability is significant but context-dependent. Organizations that still operate legacy systems running Red Hat Linux 6.0, particularly in critical infrastructure, industrial control systems, or legacy application environments, face a high risk. An attacker with local access could gain root privileges, leading to full system compromise. This could result in data breaches, unauthorized data manipulation, disruption of services, or use of the compromised system as a pivot point for further attacks within the network. Given the age of the affected version, most modern European enterprises are unlikely to be directly impacted; however, legacy systems in sectors such as manufacturing, utilities, or government agencies may still be vulnerable. The vulnerability also poses a risk in environments where physical security is weak, as an attacker with physical access can exploit it easily. The lack of a patch means that mitigation relies on compensating controls. The overall impact includes potential loss of confidentiality, integrity, and availability of critical systems, which could have cascading effects on business operations and regulatory compliance within Europe.

Mitigation Recommendations

Since no patch is available for Red Hat 6.0, European organizations should prioritize the following specific mitigation steps: 1) Upgrade or migrate all systems from Red Hat 6.0 to a supported, modern Linux distribution with active security maintenance. 2) Enforce strict physical security controls to prevent unauthorized personnel from accessing system consoles or rebooting machines. 3) Disable or restrict booting into single-user mode via bootloader configuration (e.g., GRUB) by setting password protection on bootloader menus and restricting access to boot parameters. 4) Implement BIOS/UEFI password protection and disable booting from external media to prevent bypassing OS-level controls. 5) Use centralized logging and monitoring to detect unexpected reboots or single-user mode boots. 6) Isolate legacy systems in segmented network zones with strict access controls to limit the impact of a potential compromise. 7) Conduct regular audits to identify any remaining systems running outdated OS versions and prioritize their remediation. These measures go beyond generic advice by focusing on controlling the boot process and physical access, which are critical given the nature of this vulnerability.

Need more detailed analysis?Get Pro

Threat ID: 682ca32db6fd31d6ed7df861

Added to database: 5/20/2025, 3:43:41 PM

Last enriched: 6/25/2025, 11:45:21 AM

Last updated: 7/29/2025, 6:26:27 AM

Views: 11

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats