Логотип exploitDog
bind:CVE-2001-1585
Консоль
Логотип exploitDog

exploitDog

bind:CVE-2001-1585

Количество 3

Количество 3

nvd логотип

CVE-2001-1585

больше 23 лет назад

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.

CVSS2: 6.8
EPSS: Низкий
debian логотип

CVE-2001-1585

больше 23 лет назад

SSH protocol 2 (aka SSH-2) public key authentication in the developmen ...

CVSS2: 6.8
EPSS: Низкий
github логотип

GHSA-3rg7-4f6m-6x73

около 3 лет назад

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.

EPSS: Низкий

Уязвимостей на страницу

Уязвимость
CVSS
EPSS
Опубликовано
nvd логотип
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-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.

CVSS2: 6.8
0%
Низкий
больше 23 лет назад
debian логотип
CVE-2001-1585

SSH protocol 2 (aka SSH-2) public key authentication in the developmen ...

CVSS2: 6.8
0%
Низкий
больше 23 лет назад
github логотип
GHSA-3rg7-4f6m-6x73

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.

0%
Низкий
около 3 лет назад

Уязвимостей на страницу