Unprotected SSH servers: what the Terrapin attack reveals about updates
SSH is the standard tool that administrators use to manage servers remotely. At the end of 2023, researchers at Ruhr University Bochum presented a vulnerability in the SSH protocol, the Terrapin attack. According to their measurements, millions of servers accessible via the internet were affected at the time. Updates were quickly available but in many places were not installed for a long time.
What SSH is and why it is so widespread
SSH (Secure Shell) establishes an encrypted connection to a remote computer. It is used to manage servers, network devices, firewalls and storage systems and to transfer files. Because SSH runs on almost every Linux server and many network devices, a vulnerability in the protocol affects a very large number of systems at the same time.
What the researchers in Bochum found
The Terrapin attack (CVE-2023-48795) requires an attacker to be able to intercept the connection between client and server, a so-called man-in-the-middle position, for example in an unfamiliar Wi-Fi network or a compromised network. The attacker can then remove individual messages unnoticed at the start of the connection and thus weaken protective mechanisms that both sides had actually agreed on.
Connections using certain widely used encryption methods were affected. The manufacturers of common SSH software have provided updates with additional protection, in the case of OpenSSH from version 9.6. The protection is only effective if both server and client have been updated. The researchers also published a freely available testing tool that can be used to check whether a server is vulnerable.
The real problem: missing updates
Terrapin is not an easy way into a network for attackers. However, the case shows a pattern that recurs with many security vulnerabilities: the solution is known and available but is not installed. Systems that were set up once and have “just been running” ever since are lost sight of, especially network devices, older servers and storage systems.
For private individuals, ignoring security updates for a long time is careless. In a company, it can have serious consequences, up to and including questions of liability. Anyone responsible for operating systems, whether internally or as a service provider, should install available security updates promptly, or make a conscious, documented decision on why this is not possible.
How to protect your servers
- Get an overview: Record which servers and devices run SSH or other remote access services.
- Install updates: Update SSH servers and clients as well as the firmware of network devices regularly, and document this.
- Limit accessibility: SSH access should not be openly exposed to the internet, but only reachable via VPN or from defined addresses.
- Secure sign-in: Sign in with keys instead of passwords, disable direct access for administrator accounts and, where possible, use a second factor.
- Monitor: Suspicious sign-in attempts and new security alerts should be reported and dealt with automatically.
A simple test for your company
If your employees are repeatedly prompted on their computers to install updates, this indicates that update management is not handled centrally. The same applies to servers, except that nobody sees it there. Therefore, ask for regular reports on which systems are at which update level.
Related service
Cyber Risk Check
You find out where your company stands in terms of IT security and get an overview of the measures that make sense first.