This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| openssh_vulnerability_cve-2024-6387 [03.07.2024 11:09] – [Links:] Pascal Suter | openssh_vulnerability_cve-2024-6387 [03.07.2024 11:10] (current) – [OpenSSH Vulnerability CVE-2024-6387] Pascal Suter |
|---|
| ====== OpenSSH Vulnerability CVE-2024-6387 ====== | ====== OpenSSH Vulnerability CVE-2024-6387 ====== |
| An security vulnerability from openssh versions prior to 4.4p1 was re-introduced in openssh version 8.5p1 and fnially fixed again in version 9.8p1 | An security vulnerability from openssh versions prior to 4.4p1 was re-introduced in openssh version 8.5p1 and fnially fixed again in version 9.8p1 |
| | |
| | This was [[https://www.qualys.com/regresshion-cve-2024-6387/|made public]] on July 1st 2024 by Qualys who found the issue. |
| |
| The vulnerability allows an attacker to remotely execute code with root privileges without authentication, which is of course the worst case scenario of what could go wrong with openssh. However, the exploit is very complex to trigger as it is timing related and it requires a huge amount of trial and error, causing very high network traffic and is generally more likely to crash the openssh server than to actually succeed. For this reason Red Hat classified this vulnerability only as "Important" (level 3 out of 4). Still, it is highly recommended to mitigate or patch this vulnerability right away, as the damage that can be done through it is massive. | The vulnerability allows an attacker to remotely execute code with root privileges without authentication, which is of course the worst case scenario of what could go wrong with openssh. However, the exploit is very complex to trigger as it is timing related and it requires a huge amount of trial and error, causing very high network traffic and is generally more likely to crash the openssh server than to actually succeed. For this reason Red Hat classified this vulnerability only as "Important" (level 3 out of 4). Still, it is highly recommended to mitigate or patch this vulnerability right away, as the damage that can be done through it is massive. |