CVE-2005-2666

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. Limited direct impact.

Exploit odds

1.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2005-08-23 04:00 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 22:15 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.2% in the next 30 days (EPSS).
• Severity: 1.2 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2005-08-23 04:00 UTC

Last modified

2026-06-16 22:15 UTC

Exploit probability

1.2% · EPSS, next 30 days

Weakness

CWE-255

Record status

Modified

Affected

• Openbsd OpenSSH 3.0
• Openbsd OpenSSH 3.0.1
• Openbsd OpenSSH 3.0.1p1
• Openbsd OpenSSH 3.0.2
• Openbsd OpenSSH 3.0.2p1
• Openbsd OpenSSH 3.0p1
• Openbsd OpenSSH 3.1
• Openbsd OpenSSH 3.1p1

Attack profile CVSS 2.0 · 1.2

Attack vector

Local

Complexity

High

Authentication

None

Confidentiality

Partial

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2005-2666.md and follow it. Check whether this project is affected by CVE-2005-2666. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge