c0r0n3r
"The DHEat attack remains viable against most SSH installations, as default settings are inadequate at deflecting it. Very little bandwidth is needed to cause a dramatic effect on targets, including those with a high degree of resources. Hence, SSH services should be blocked from external access whenever possible. Furthermore, connection rate limiting should always be applied regardless of network segmentation, as per the central principles of Zero Trust."
D(HE)at: A Practical DoS Attack on the Finite Field Diffie–Hellman Key Exchange
CryptoLyzer 0.12 –= SSLyze and testssl.sh and SSH-audit and Mozilla observatory
Server TLS settings analyzer CryptoLyzer with OpenVPN support has released
CryptoLyzer 0.8.5 with browser (Chromium, Firefox, Opera) compatibility checker
Factorization (DCQF) of a 48-bit integer using 10 trapped-ion qubits
Chinese researchers: RSA is breakable. Others: Do not panic
OpenSSL: How to Configure LS Groups to Be Resistant to the DHEat Attack
There are another tools (open source and SaaS) on OWASP Transport Layer Protection Cheat Sheet page[2].
[1] https://gitlab.com/coroner/cryptolyzer
[2] https://cheatsheetseries.owasp.org/cheatsheets/Transport_Lay...
Websites, mail servers, and other Transport Layer Security (TLS) dependent services that support Diffie-Hellman key exchange using ephemeral keys (DHE cipher suites) are at risk of the DHEat attack. Services using other cryptographic protocols can also be affected.
* Secure Shell (SSH) services support Diffie-Hellman key exchange methods. * Internet Protocol Security (IPsec) services offer DH groups. * OpenVPN servers support Diffie-Hellman key exchange in the control channel (DHE TLS ciphers).
How bad is it?
The CVSS 3.1 base score of CVE-2002-20001 is 7.5, indicating high severity but is not critical. However, it should be mentioned that a denial-of-service attack affects only availability. Still, confidentiality, integrity, and scope are not is affected and cannot achieve a higher base score. However, an attacker can exploit the vulnerability and perform a denial-of-service attack with a low-bandwidth network connection without authentication, privilege, or user interaction. Along with the fact that this vulnerability cannot be fixed, as it exploits a particularity of the Diffie-Hellman key exchange algorithm, it can be mitigated in some ways.
DoS attack against Diffie-Hellman protocol
Websites, mail servers, and other Transport Layer Security (TLS) dependent services that support Diffie-Hellman key exchange using ephemeral keys (DHE cipher suites) are at risk of the DHEat attack. Services using other cryptographic protocols can also be affected.
* Secure Shell (SSH) services support Diffie-Hellman key exchange methods. * Internet Protocol Security (IPsec) services offer DH groups. * OpenVPN servers support Diffie-Hellman key exchange in the control channel (DHE TLS ciphers).
DoS attack against Diffie-Hellman protocol
https://dev.to/coroner/why-do-certificate-revocation-checkin...