CVE-2005-2666: SSH, as implemented in OpenSSH before 4.0 and possibly other implementations, stores hostnames, IP addresses, and keys in plaintext in the…
Noroxi assessment
Priority: Monitor (action score 4/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 68.1% of all records.
- Special conditions such as timing or configuration are required.
- Fixed version: openssh (Debian:12) 1:4.0p1-1; openssh (Red Hat:enterprise_linux:4::as) 0:3.9p1-8.RHEL4.20; openssh-askpass (Red Hat:enterprise_linux:4::as) 0:3.9p1-8.RHEL4.20.
Low priority for now. Upgrade to openssh (Debian:12) 1:4.0p1-1; openssh (Red Hat:enterprise_linux:4::as) 0:3.9p1-8.RHEL4.20; openssh-askpass (Red Hat:enterprise_linux:4::as) 0:3.9p1-8.RHEL4.20 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 23, 2005
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 68th percentile
- CWE
- CWE-255
Report tools
Action score
4
Low priority for now.
- CVSS
- 4 / 40 · 1.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is OpenSSH on your server exposed to the internet?Run a port scan
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openbsd | openssh | cpe:2.3:a:openbsd:openssh |
Is OpenSSH on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openbsd openssh3.0
- openbsd openssh3.0.1
- openbsd openssh3.0.1p1
- openbsd openssh3.0.2
- openbsd openssh3.0.2p1
- openbsd openssh3.0p1
- openbsd openssh3.1
- openbsd openssh3.1p1
+12 more rows
- openbsd openssh3.2
- openbsd openssh3.2.2p1
- openbsd openssh3.2.3p1
- openbsd openssh3.3
- openbsd openssh3.3p1
- openbsd openssh3.4
- openbsd openssh3.4p1
- openbsd openssh3.5
- openbsd openssh3.5p1
- openbsd openssh3.6
- openbsd openssh3.6.1
- openbsd openssh3.6.1p1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | openssh | before 1:4.0p1-1 | 1:4.0p1-1 |
| Red Hat:enterprise_linux:4::as | openssh | before 0:3.9p1-8.RHEL4.20 | 0:3.9p1-8.RHEL4.20 |
| Red Hat:enterprise_linux:4::as | openssh-askpass | before 0:3.9p1-8.RHEL4.20 | 0:3.9p1-8.RHEL4.20 |
| Red Hat:enterprise_linux:4::as | openssh-askpass-gnome | before 0:3.9p1-8.RHEL4.20 | 0:3.9p1-8.RHEL4.20 |
| Red Hat:enterprise_linux:4::as | openssh-clients | before 0:3.9p1-8.RHEL4.20 | 0:3.9p1-8.RHEL4.20 |
| Red Hat:enterprise_linux:4::as | openssh-debuginfo | before 0:3.9p1-8.RHEL4.20 | 0:3.9p1-8.RHEL4.20 |
| Red Hat:enterprise_linux:4::as | openssh-server | before 0:3.9p1-8.RHEL4.20 | 0:3.9p1-8.RHEL4.20 |
Same product
openbsd: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-123158sshd in OpenSSH before 10.6p2 on Linux, when musl libc is used without PAM, lacks a workaround for a password authentication bypass…KEV68This week
- CVE-2023-38408The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if…63This week
- CVE-2018-15473OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after…60This week
Published before and after this one in the same product
- ← EarlierCVE-2004-2069Dec 31, 2004 · sshd.c in OpenSSH 3.6.1p2 and 3.7.1p2 and possibly other versions, when using privilege separation, does not properly signal the…21Monitor
- ← EarlierCVE-2004-2760Dec 31, 2004 · sshd in OpenSSH 3.5p1, when PermitRootLogin is disabled, immediately closes the TCP connection after a root login attempt with the correct…30Monitor
- Later →CVE-2005-2797Sep 6, 2005 · OpenSSH 4.0, and other versions before 4.2, does not properly handle dynamic port forwarding ("-D" option) when a listen address is not…21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:openssh | 1:4.0p1-1 · Debian:12 | Package registry (OSV) |
| red hat:openssh | 0:3.9p1-8.RHEL4.20 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:openssh-askpass | 0:3.9p1-8.RHEL4.20 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:openssh-askpass-gnome | 0:3.9p1-8.RHEL4.20 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:openssh-clients | 0:3.9p1-8.RHEL4.20 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:openssh-debuginfo | 0:3.9p1-8.RHEL4.20 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:openssh-server | 0:3.9p1-8.RHEL4.20 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- P · data can be read
- Integrity
- none
- Availability
- none
- Attack complexity
- High
- Confidentiality impact
- P
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-255 · Credentials Management ErrorsCVSS vector
AV:L/AC:H/Au:N/C:P/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.