Security News

Severe OpenSSH Flaw ‘regreSSHion’ Puts Millions of Linux Systems at Risk

OpenSSH regreSSHion, CVE-2024-6387, lets attackers run code as root on sshd. See affected versions 8.5p1 to 9.7p1, the 8.1 score and how to cut the risk.

Brandefense logo Updated 3 Min Read
openssh reggession

OpenSSH has a critical flaw called regreSSHion, tracked as CVE-2024-6387, that lets an unauthenticated attacker run code as root on a server over the network. It affects OpenSSH server versions 8.5p1 up to, but not including, 9.8p1, on glibc-based Linux systems. NVD scores it 8.1 (High). Updating to OpenSSH 9.8p1 or later fixes it.

A recently discovered critical vulnerability known as ‘regreSSHion’ puts millions of Linux systems at severe risk. Identified as CVE-2024-6387, this flaw affects the OpenSSH server (sshd) on glibc-based Linux systems, allowing unauthenticated attackers to gain root access and potentially take complete control of the affected machines.

What is the OpenSSH regreSSHion vulnerability, CVE-2024-6387?

The vulnerability, a signal handler race condition in OpenSSH’s server (sshd), impacts sshd in its default configuration and requires no user interaction. This race condition enables unauthenticated remote code execution (RCE) as root, giving attackers full control over the affected systems. This flaw exists in OpenSSH versions from 8.5p1 up to, but not including, 9.8p1, reintroducing a previously patched issue from CVE-2006-5051.

CVE-2024-6387 at a glance
CVE.
CVE-2024-6387, known as regreSSHion.
Product.
OpenSSH server (sshd) on glibc-based Linux.
Affected.
OpenSSH 8.5p1 up to, but not including, 9.8p1.
Impact.
Unauthenticated remote code execution as root.
NVD score.
8.1 (High).
Fix.
Update to OpenSSH 9.8p1 or later.

Security researchers noted that it is an unauthenticated RCE that grants full root access, affects the default configuration and does not require user interaction.

The scope of the vulnerability is extensive, with Internet-wide scans identifying many potentially vulnerable OpenSSH server instances, a share of them exposed to the Internet.

Successful exploitation of regreSSHion could lead to complete system compromise, enabling attackers to install malware, manipulate data, and establish backdoors for persistent access. The ability to propagate through networks and bypass security mechanisms makes this vulnerability particularly dangerous for enterprises and individuals alike.

Exploitation Challenges and Future Risks

Although exploiting this vulnerability is challenging due to its remote race condition nature, requiring multiple attempts for a successful attack, advancements in deep learning could significantly increase exploitation rates. These technologies may provide attackers with sophisticated methods to leverage such security flaws, making timely mitigation crucial.

How do you reduce the risk from regreSSHion?

To address the regreSSHion vulnerability, enterprises should adopt a focused and layered security approach:

  • Patch Management: Promptly apply available patches for OpenSSH and prioritize regular update processes to ensure all systems are protected.
  • Enhanced Access Control: Limit SSH access through network-based controls to minimize attack risks.
  • Network Segmentation and Intrusion Detection: Implement network segmentation to restrict unauthorized access and lateral movements within critical environments. Deploy intrusion detection systems to monitor and alert on unusual activities indicative of exploitation attempts.

By implementing these measures, organizations can significantly reduce the risk posed by this critical vulnerability and protect their systems from potential exploitation.

Conclusion

The discovery of CVE-2024-6387 underscores the importance of diligent cybersecurity practices and the necessity of safeguarding and continuously monitoring systems. Organizations must act promptly to patch vulnerable systems and strengthen their security posture to mitigate the risks associated with this severe vulnerability.

Recommendations

  1. Regularly update and patch all systems to address known vulnerabilities.
  2. Implement strong access controls and limit SSH access to essential personnel only.
  3. Utilize network segmentation and intrusion detection systems to swiftly respond to suspicious activities.

Frequently Asked Questions.

What is the OpenSSH regreSSHion vulnerability?

It is CVE-2024-6387, a signal handler race condition in the OpenSSH server (sshd). It can allow unauthenticated remote code execution as root.

Which OpenSSH versions are affected?

OpenSSH 8.5p1 up to, but not including, 9.8p1. The OpenSSH 9.8 release notes list portable OpenSSH 8.5p1 through 9.7p1.

How severe is CVE-2024-6387?

NVD lists a CVSS 3.1 base score of 8.1 (High), with high attack complexity. The OpenSSH release notes call it a critical vulnerability.

How hard is it to exploit regreSSHion?

It is hard, because it is a remote race condition that needs many attempts. The OpenSSH release notes describe a demonstrated attack on 32-bit Linux with glibc taking on average 6 to 8 hours of continuous connections.

How do I protect my systems?

Update OpenSSH to 9.8p1 or later and limit SSH access with network controls. Network segmentation and intrusion detection add further protection.

Sources

  1. 1 NVD record for CVE-2024-6387 (API view)
  2. 2 OpenSSH 9.8 release notes
  3. 3 NVD record for CVE-2006-5051 (API view)