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 cve@mitre.org

Affected Software	Affected Version	How to fix
Openbsd Openssh	=3.8
Openbsd Openssh	=3.8.1p1
Openbsd Openssh	=3.1
Openbsd Openssh	=3.0.2p1
Openbsd Openssh	=3.8.1
Openbsd Openssh	=3.7.1p2
Openbsd Openssh	=3.2.3p1
Openbsd Openssh	=3.1p1
Openbsd Openssh	=3.6.1p2
Openbsd Openssh	=3.9
Openbsd Openssh	=3.0
Openbsd Openssh	=3.2
Openbsd Openssh	=3.6
Openbsd Openssh	=3.7
Openbsd Openssh	=3.5p1
Openbsd Openssh	=3.0.1p1
Openbsd Openssh	=3.3
Openbsd Openssh	=3.2.2p1
Openbsd Openssh	=3.9.1p1
Openbsd Openssh	=3.0.2
Openbsd Openssh	=3.4p1
Openbsd Openssh	=3.6.1p1
Openbsd Openssh	=3.0.1
Openbsd Openssh	=3.6.1
Openbsd Openssh	=3.7.1
Openbsd Openssh	=3.4
Openbsd Openssh	=3.5
Openbsd Openssh	=3.0p1
Openbsd Openssh	=3.3p1
Openbsd Openssh	=3.9.1

Remedy

http://nms.csail.mit.edu/projects/ssh/

Never miss a vulnerability like this again

Company

Resources

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.