{"id":2331,"date":"2024-07-03T21:40:11","date_gmt":"2024-07-03T21:40:11","guid":{"rendered":"https:\/\/amaru.co.nz\/fj\/?post_type=threat-intelligence&p=2331"},"modified":"2024-07-12T00:13:08","modified_gmt":"2024-07-12T00:13:08","slug":"security-advisory-regresshion-remote-unauthenticated-code-execution-vulnerability-in-openssh","status":"publish","type":"threat-intelligence","link":"https:\/\/amaru.co.nz\/fj\/blog\/threat-intelligence\/security-advisory-regresshion-remote-unauthenticated-code-execution-vulnerability-in-openssh\/","title":{"rendered":"[ Security Advisory ] regreSSHion: Remote Unauthenticated Code Execution Vulnerability in OpenSSH"},"content":{"rendered":"
\/\/ Overview\u00a0<\/strong><\/h5>\n

On June 7th, 2024, Qualys Threat Researcher Unit [1<\/a>] discovered a Remote Unauthenticated Code Execution (RCE) vulnerability in OpenSSH\u2019s server (sshd) in glibc-based Linux systems. This vulnerability, being a single handler race condition in OpenSSH\u2019s server (sshd), allows unauthenticated remote code execution (RCE) as root on glibc-based Linux systems and affects sshd in its default configuration. The vulnerability is tracked as CVE-2024-6387 and carries a CVSSv3 score of 8.1.<\/p>\n

Out of the 14 million potentially vulnerable sshd instances that show up on Censys and Shodan scans, it is believed that around 700,000 of these internet-facing instances could feasibly be hit by this vulnerability [1<\/a>]. However, it\u2019s important to note that as of July 1st, 2024, no confirmed reports of exploitation have been reported.<\/p>\n

This vulnerability has been named \u2018regreSSHion\u2019 as it has been identified as a regression of the previously patched vulnerability tracker as CVE-2006-5051, reported in 2006. The term regression means that a flaw, once fixed, has reappeared in a later software release, typically due to changes or updates that inadvertently reintroduce the issue.<\/p>\n

\/\/ What you should do\u00a0<\/strong><\/h5>\n

Customers using affected versions of OpenSSH are recommended to apply the following mitigations at the earliest possible convenience:<\/p>\n