SSH (OpenSSH) · CVSS 5.9 · published 18 December 2023
Terrapin: CVE-2023-48795
A prefix truncation attack on the SSH protocol: an attacker in the network path can remove messages at the start of the encrypted session and weaken its security extensions. Both the client and the server need the fix. Below is its status on each Linux distribution past end of life, from the vendors' own security trackers.
- 6end-of-life systems without a free fix
- 3fixed or not affected
Terrapin on end-of-life Linux
| Distribution | Status | Details |
|---|---|---|
| CentOS 6 | Not fixed | Red Hat: out of support scope |
| CentOS 7 | Not fixed | Red Hat: out of support scope |
| RHEL 7 | Not fixed | Red Hat: out of support scope |
| CentOS 8 | No free fix | Red Hat fixed it on 30 January 2024, after this release's end of life |
| Ubuntu 16.04 | Fixed only in Ubuntu Pro | 1:7.2p2-4ubuntu2.10+esm5 |
| Ubuntu 18.04 | Fixed only in Ubuntu Pro | 1:7.6p1-4ubuntu0.7+esm3 |
| Ubuntu 20.04 | Fixed | 1:8.2p1-4ubuntu0.10 |
| Debian 10 | Fixed | 1:7.9p1-10+deb10u4, DLA-3694-1 |
| Debian 11 | Fixed | 1:8.4p1-5+deb11u3, DSA-5586-1 |
From the Red Hat security data (CentOS and RHEL), the Ubuntu CVE tracker and the Debian security tracker, 29 October 2026. CentOS received Red Hat's fixes only until its own end of life; later fixes went to paid Red Hat support. Fixes marked Ubuntu Pro need a paid subscription. Where a tracker has no entry, the version in the distribution's repository is checked against the NVD range.
The OpenSSH versions we track
| Version | CVE-2023-48795 |
|---|---|
| OpenSSH 5.3p1 | Affected |
| OpenSSH 7.2p2 | Affected |
| OpenSSH 7.4p1 | Affected |
| OpenSSH 7.6p1 | Affected |
| OpenSSH 7.9p1 | Affected |
| OpenSSH 8.0p1 | Affected |
| OpenSSH 8.2p1 | Affected |
| OpenSSH 8.4p1 | Affected |
For the upstream version, according to the US National Vulnerability Database. A distribution package may carry its own fix; the table above shows that.
What the NVD record says
The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.
Score 5.9 (Medium), published 18 December 2023. Read the NVD entry
Affected upstream versions of SSH (OpenSSH)
- openssh before 9.6
What you can do
Keep SSH (OpenSSH), patched
Where the table shows no free fix, we backport it to the package you run, built and tested before delivery. A fix for a new vulnerability arrives within 48 hours of your order, or within 24 hours with priority delivery.
Upgrade
Move to a supported release once your applications can make the jump. Our fixes keep you safe while you plan it.
Assess first
Our assessment shows which vulnerabilities are real on your servers, what else is past end of life, and the remediation plan.