CVE-2016-20012
Medium · 5.3CVSS
5.3
EPSS
5.3%
Published
Sep 15, 2021
CISA due date
—
Cloudanix analysis
Attackers can quietly test whether guessed usernames and keys are accepted by a server, helping them find real accounts to target later.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Low
- Impact
- Data Exposure
- Component
- Network Service
- Class
- Information Disclosure
- Remediation
- No Fix Yet
- Effort
- Other
- Patch risk
- Other
What it actually does
The flaw permits remote unauthenticated attackers to determine whether a guessed username and public key pair is valid on the server by observing whether an authentication challenge is issued, enabling low-noise user and key enumeration.
Why it matters to the business
Attackers can silently map valid accounts across many systems, increasing the likelihood of targeted follow-on attacks and lengthening the time needed to detect reconnaissance activity.
How an attack unfolds
An attacker who suspects a username and associated public key sends a crafted SSH authentication request; the server responds with a challenge only for valid combinations, confirming the guess without triggering a full login attempt.
How to fix it
Upgrade affected packages to the fixed versions kubernetes-csi-livenessprobe (Chainguard) 2.13.0-r1 or kubernetes-csi-livenessprobe (Wolfi) 2.13.0-r1; apply vendor patches that alter authentication behavior to eliminate distinguishable challenge responses.
How to confirm the fix worked
Confirm the installed package version meets or exceeds the fixed release; perform controlled authentication probes with known-valid and known-invalid key pairs to verify uniform server behavior regardless of key validity.
Typical attack path
- Obtain or guess candidate username and public key pairs from prior breaches or OSINT
- Send SSH authentication requests containing the guessed pair to the target server
- Observe whether the server issues a challenge response
- Record confirmed valid pairs for subsequent targeted attacks such as password spraying or key-based brute force
How to detect it
Examine SSH daemon logs for authentication attempts that receive challenge responses without subsequent successful logins; correlate with external reconnaissance indicators such as repeated connection attempts from the same sources.
What your security team should do
- Prioritize patching the listed packages within standard change windows given the public exploit availability
- Review SSH configurations to disable public-key authentication where not required or enforce stricter key management
- Monitor authentication logs for repeated probes that do not result in successful sessions
The record
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
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:10 | openssh | 0 | No fix |
| Debian:11 | openssh | 0 | No fix |
| Debian:12 | openssh | 0 | No fix |
| Debian:13 | openssh | 0 | No fix |
| Debian:14 | openssh | 0 | No fix |
| Ubuntu:18.04:LTS | openssh-ssh1 | 0 | No fix |
| Ubuntu:20.04:LTS | openssh | 0 | No fix |
| Ubuntu:20.04:LTS | openssh-ssh1 | 0 | No fix |
| Ubuntu:22.04:LTS | openssh | 0 | No fix |
| Ubuntu:22.04:LTS | openssh-ssh1 | 0 | No fix |
| Ubuntu:Pro:14.04:LTS | openssh | 0 | No fix |
| Ubuntu:Pro:16.04:LTS | openssh | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | openssh | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | openssh-ssh1 | 0 | No fix |
| Ubuntu:Pro:20.04:LTS | openssh | 0 | No fix |
| Ubuntu:Pro:20.04:LTS | openssh-ssh1 | 0 | No fix |
| Ubuntu:Pro:22.04:LTS | openssh-ssh1 | 0 | No fix |
| Ubuntu:Pro:FIPS-updates:18.04:LTS | openssh | 0 | No fix |
| Ubuntu:Pro:FIPS-updates:20.04:LTS | openssh | 0 | No fix |
| Ubuntu:Pro:FIPS:16.04:LTS | openssh | 0 | No fix |
| Ubuntu:Pro:FIPS:18.04:LTS | openssh | 0 | No fix |
| Ubuntu:Pro:FIPS:20.04:LTS | openssh | 0 | No fix |
Related vulnerabilities
- CVE-2023-51767 OpenSSH through 10.0, when common types of DRAM are used, might allow row hammer attacks… Also affects openssh
- CVE-2023-51385 In ssh in OpenSSH before 9.6, OS command injection might occur if a user name or host… Also affects openssh
- CVE-2021-36368 An issue was discovered in OpenSSH before 8.9. Also affects openssh
- CVE-2021-41617 sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are… Also affects openssh
- CVE-2017-15906 The process_open function in sftp-server.c in OpenSSH before 7.6 does not properly… Also affects openssh
- CVE-2016-10011 authfile.c in sshd in OpenSSH before 7.4 does not properly consider the effects of… Also affects openssh
- CVE-2016-10012 The shared memory manager (associated with pre-authentication compression) in sshd in… Also affects openssh
- CVE-2016-10009 Untrusted search path vulnerability in ssh-agent.c in ssh-agent in OpenSSH before 7.4… Also affects openssh