Description
SSH protocol 2 (aka SSH-2) public key authentication in the development snapshot of OpenSSH 2.3.1, available from 2001-01-18 through 2001-02-08, does not perform a challenge-response step to ensure that the client has the proper private key, which allows remote attackers to bypass authentication as other users by supplying a public key from that user's authorized_keys file.
Metrics
CVSS 2.0 6.8/10
AV:N/AC:M/Au:N/C:P/I:P/A:PWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
References
- http://archives.neohapsis.com/archives/bugtraq/2001-02/0159.html
- http://online.securityfocus.com/bid/2356Patch
- http://www.openbsd.org/advisories/ssh_bypass.txtPatch
- https://exchange.xforce.ibmcloud.com/vulnerabilities/6084
- http://archives.neohapsis.com/archives/bugtraq/2001-02/0159.html
- http://online.securityfocus.com/bid/2356Patch
- http://www.openbsd.org/advisories/ssh_bypass.txtPatch
- https://exchange.xforce.ibmcloud.com/vulnerabilities/6084
Timeline
- Published
- Dec 31, 2001
- Last modified
- Jun 16, 2026
- NVD status
- Modified