SSH Protocol Version 1 Supported
The SSH server still accepts version 1 of the SSH protocol, which has design flaws that version 2 corrected and is no longer supported by current SSH software.
| Severity | Medium |
| CVSS 3.1 | 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Open in the calculator |
| CVSS 4.0 | 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-327: Use of a Broken or Risky Cryptographic Algorithm |
| OWASP Top 10 | A04:2025 Cryptographic Failures |
| MITRE ATT&CK | T1557 Adversary-in-the-Middle, T1040 Network Sniffing |
| Category | Cryptographic Failures |
Description
The SSH server accepts connections using version 1 of the SSH protocol (SSH-1). SSH-1 was replaced by SSH-2, standardised in 2006, because of weaknesses in the protocol's design rather than in any one implementation: it protects message integrity with a CRC-32 checksum instead of a cryptographic message authentication code, which has been shown to allow data to be inserted into an encrypted session, and it relies on ciphers and key sizes now regarded as weak.
Published attacks against SSH-1 let an attacker who can intercept or modify traffic insert data into sessions in this way and, against some implementations, recover the session key and so read the traffic, including any passwords sent. The attack needs an intercepting position and a client that connects using SSH-1, which limits the likelihood, although a server that accepts both versions lets any client configured to prefer SSH-1 use it.
Current OpenSSH releases no longer contain SSH-1 at all, so a server that offers it is usually an old release or another SSH implementation, often on a network device, appliance or embedded system. Software old enough to offer SSH-1 is also likely to carry other known vulnerabilities, and SSH-1 implementations have historically been the subject of remotely exploitable flaws.
The versions a server accepts are shown in its identification banner. A banner beginning SSH-1.99- means the server accepts both SSH-2 and SSH-1, while SSH-1.5- or similar means it accepts only SSH-1. Support can be confirmed with the Nmap sshv1 script or with a client that can still request SSH-1, and scanners report it as SSH protocol version 1 supported.
Remediation
Disable SSH-1 so that only SSH-2 is accepted:
- Upgrade the SSH server to a current, supported release; releases that no longer implement SSH-1 remove the issue entirely.
- On older OpenSSH releases that cannot be upgraded straight away, set
Protocol 2insshd_configand restart the service. - On Cisco IOS devices, use
ip ssh version 2; on other network devices and appliances, use the vendor's equivalent setting, or upgrade the firmware where SSH-1 cannot be disabled. - Identify any clients, scripts or devices that still connect with SSH-1 and upgrade or replace them before the change, so that they do not lead to SSH-1 being re-enabled.
While the change is pending, restrict SSH on the affected systems to management networks. Confirm the fix by checking that the banner now begins SSH-2.0- and that the Nmap sshv1 script, or a client forced to use SSH-1, can no longer connect.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.