Description
OpenSSH before 2.9.9, while using keypairs and multiple keys of different types in the ~/.ssh/authorized_keys2 file, may not properly handle the "from" option associated with a key, which could allow remote attackers to login from unauthorized IP addresses.
Products
- OpenBSD OpenSSH
- OpenBSD OpenSSH
- OpenBSD OpenSSH 1.2.1
- OpenBSD OpenSSH 1.2.27
- OpenBSD OpenSSH 1.2.2
- OpenBSD OpenSSH 1.2.2
- OpenBSD OpenSSH 1.2.2 p1
- OpenBSD OpenSSH 1.2.3
- OpenBSD OpenSSH 1.2.3
- OpenBSD OpenSSH 1.2.3 p1
- OpenBSD OpenSSH 1.2
- OpenBSD OpenSSH 1.3
- OpenBSD OpenSSH 1.5.7
- OpenBSD OpenSSH 1.5.8
- OpenBSD OpenSSH 1.5
- OpenBSD OpenSSH 2.1.0 -
- OpenBSD OpenSSH 2.1.0 p1
- OpenBSD OpenSSH 2.1.1
- OpenBSD OpenSSH 2.1.1
- OpenBSD OpenSSH 2.1.1 p1
- OpenBSD OpenSSH 2.1.1 p2
- OpenBSD OpenSSH 2.1.1 p3
- OpenBSD OpenSSH 2.1.1 p4
- OpenBSD OpenSSH 2.1
- OpenBSD OpenSSH 2.2.0 -
- OpenBSD OpenSSH 2.2.0 p1
- OpenBSD OpenSSH 2.2
- OpenBSD OpenSSH 2.3.0
- OpenBSD OpenSSH 2.3.0 p1
- OpenBSD OpenSSH 2.3.1
- OpenBSD OpenSSH 2.3
- OpenBSD OpenSSH 2.5.1
- OpenBSD OpenSSH 2.5.1
- OpenBSD OpenSSH 2.5.1 p1
- OpenBSD OpenSSH 2.5.1 p2
- OpenBSD OpenSSH 2.5.2
- OpenBSD OpenSSH 2.5.2
- OpenBSD OpenSSH 2.5.2 p2
- OpenBSD OpenSSH 2.5
- OpenBSD OpenSSH 2.9.9
- OpenBSD OpenSSH 2.9.9
- OpenBSD OpenSSH 2.9.9 p1
- OpenBSD OpenSSH 2.9.9 p2
- OpenBSD OpenSSH 2.9
- OpenBSD OpenSSH 2.9
- OpenBSD OpenSSH 2.9 p1
- OpenBSD OpenSSH 2.9 p2
- OpenBSD OpenSSH 2
Questions to Ask Vendors
- Can you confirm whether your systems are affected by CVE-2001-1380, and if so, what steps are you currently taking to mitigate this vulnerability?
- What is your estimated timeline for fully resolving CVE-2001-1380 in your products or services, and how will you communicate updates on this issue to us as your customer?
Recommended Actions
- Check out the advisory links provided below.
References