Cloudanix VulnDB

CVE-2016-20012

Medium · 5.3

CVSS

5.3

EPSS

5.3%

Published

Sep 15, 2021

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

Attackers can quietly test whether guessed usernames and keys are accepted by a server, helping them find real accounts to target later.

Exploit Available
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

  1. Obtain or guess candidate username and public key pairs from prior breaches or OSINT
  2. Send SSH authentication requests containing the guessed pair to the target server
  3. Observe whether the server issues a challenge response
  4. 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