CVE-2016-20012
First published: Wed Sep 15 2021(Updated: )
** DISPUTED ** OpenSSH through 8.7 allows remote attackers, who have a suspicion that a certain combination of username and public key is known to an SSH server, to test whether this suspicion is correct. This occurs because a challenge is sent only when that combination could be valid for a login session. NOTE: the vendor does not recognize user enumeration as a vulnerability for this product.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Openbsd Openssh | <=8.7 | |
| NetApp Clustered Data ONTAP | ||
| Netapp Hci Management Node | ||
| NetApp ONTAP Select Deploy administration utility | ||
| Netapp Solidfire | ||
| <=8.7 | ||
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/openssh/openssh-portable/blob/d0fffc88c8fe90c1815c6f4097bc8cbcabc0f3dd/auth2-pubkey.c#L261-L265
- https://github.com/openssh/openssh-portable/pull/270
- https://github.com/openssh/openssh-portable/pull/270#issuecomment-920577097
- https://github.com/openssh/openssh-portable/pull/270#issuecomment-943909185
- https://rushter.com/blog/public-ssh-keys/
- https://security.netapp.com/advisory/ntap-20211014-0005/
- https://utcc.utoronto.ca/~cks/space/blog/tech/SSHKeysAreInfoLeak
- https://www.openwall.com/lists/oss-security/2018/08/24/1
Frequently Asked Questions
What is the vulnerability ID of this OpenSSH vulnerability?
The vulnerability ID is CVE-2016-20012.
What is the severity rating of CVE-2016-20012?
The severity rating of CVE-2016-20012 is medium with a score of 5.3.
How does this vulnerability in OpenSSH manifest?
This vulnerability allows remote attackers to test the validity of a certain combination of username and public key in an SSH server.
Which versions of OpenSSH are affected by CVE-2016-20012?
OpenSSH up to version 8.7 is affected by CVE-2016-20012.
Is there a fix for this vulnerability?
Yes, the fix for this vulnerability can be found in the OpenSSH source code.
- collector/nvd-index
- agent/references
- agent/type
- agent/first-publish-date
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/author
- agent/severity
- agent/last-modified-date
- agent/remedy
- agent/status
- agent/softwarecombine
- agent/description
- agent/event
- agent/tags
- status/disputed
- vendor/openbsd
- canonical/openbsd openssh
- version/openbsd openssh/8.7
- vendor/netapp
- canonical/netapp clustered data ontap
- canonical/netapp hci management node
- canonical/netapp ontap select deploy administration utility
- canonical/netapp solidfire