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 users authorized_keys file.
Weakness
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Openssh | Openbsd | 2.3.1 (including) | 2.3.1 (including) |
Potential Mitigations
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/114.html
- https://cwe.mitre.org/data/definitions/115.html
- https://cwe.mitre.org/data/definitions/151.html
- https://cwe.mitre.org/data/definitions/194.html
- https://cwe.mitre.org/data/definitions/22.html
- https://cwe.mitre.org/data/definitions/57.html
- https://cwe.mitre.org/data/definitions/593.html
- https://cwe.mitre.org/data/definitions/633.html
- https://cwe.mitre.org/data/definitions/650.html
- https://cwe.mitre.org/data/definitions/94.html
References
- http://archives.neohapsis.com/archives/bugtraq/2001-02/0159.html
- http://online.securityfocus.com/bid/2356
- http://www.openbsd.org/advisories/ssh_bypass.txt
- https://exchange.xforce.ibmcloud.com/vulnerabilities/6084
- http://archives.neohapsis.com/archives/bugtraq/2001-02/0159.html
- http://online.securityfocus.com/bid/2356
- http://www.openbsd.org/advisories/ssh_bypass.txt
- https://exchange.xforce.ibmcloud.com/vulnerabilities/6084