First published: Thu Jan 18 2001(Updated: )
SSH before 2.0 disables host key checking when connecting to the localhost, which allows remote attackers to silently redirect connections to the localhost by poisoning the client's DNS cache.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
SSH (Secure Shell) | =1.2.24 | |
SSH (Secure Shell) | =1.2.25 | |
SSH (Secure Shell) | =1.2.26 | |
SSH (Secure Shell) | =1.2.27 | |
SSH (Secure Shell) | =1.2.28 | |
SSH (Secure Shell) | =1.2.29 | |
SSH (Secure Shell) | =1.2.30 | |
SSH (Secure Shell) | =1.2.31 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2001-1474 has been classified as a high severity vulnerability due to its potential to redirect user connections to a malicious server.
To fix CVE-2001-1474, upgrade your SSH client to a version that includes host key checking for localhost connections.
CVE-2001-1474 affects SSH versions before 2.0, specifically versions 1.2.24 through 1.2.31.
Users affected by CVE-2001-1474 may unknowingly connect to a malicious server due to DNS cache poisoning.
CVE-2001-1474 allows attackers to silently redirect SSH connections by manipulating the DNS resolution process.