1.2
CWE
255
Advisory Published
Updated

CVE-2005-2666

First published: Tue Aug 23 2005(Updated: )

SSH, as implemented in OpenSSH before 4.0 and possibly other implementations, stores hostnames, IP addresses, and keys in plaintext in the known_hosts file, which makes it easier for an attacker that has compromised an SSH user's account to generate a list of additional targets that are more likely to have the same password or key.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
OpenSSH=3.0
OpenSSH=3.0.1
OpenSSH=3.0.1p1
OpenSSH=3.0.2
OpenSSH=3.0.2p1
OpenSSH=3.0p1
OpenSSH=3.1
OpenSSH=3.1p1
OpenSSH=3.2
OpenSSH=3.2.2p1
OpenSSH=3.2.3p1
OpenSSH=3.3
OpenSSH=3.3p1
OpenSSH=3.4
OpenSSH=3.4p1
OpenSSH=3.5
OpenSSH=3.5p1
OpenSSH=3.6
OpenSSH=3.6.1
OpenSSH=3.6.1p1
OpenSSH=3.6.1p2
OpenSSH=3.7
OpenSSH=3.7.1
OpenSSH=3.7.1p2
OpenSSH=3.8
OpenSSH=3.8.1
OpenSSH=3.8.1p1
OpenSSH=3.9
OpenSSH=3.9.1
OpenSSH=3.9.1p1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2005-2666?

    CVE-2005-2666 is considered a moderate severity vulnerability due to the exposure of sensitive information in plaintext.

  • How do I fix CVE-2005-2666?

    To mitigate CVE-2005-2666, upgrade to OpenSSH version 4.0 or later which addresses this vulnerability.

  • What does CVE-2005-2666 exploit?

    CVE-2005-2666 exploits the storage of hostnames, IP addresses, and keys in plaintext in the known_hosts file of OpenSSH.

  • Which versions of OpenSSH are affected by CVE-2005-2666?

    CVE-2005-2666 affects OpenSSH versions prior to 4.0.

  • What are the potential risks associated with CVE-2005-2666?

    The risks associated with CVE-2005-2666 include unauthorized access, as attackers can easily identify and target additional systems using the exposed information.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203