CVE-2016-6210

CVE Enrichment

CVSS: 5.9 MEDIUM
EPSS: 88.94%
EPSS Percentile: 99.78%
CISA KEV: Not listed

Description

sshd in OpenSSH before 7.3, when SHA256 or SHA512 are used for user password hashing, uses BLOWFISH hashing on a static password when the username does not exist, which allows remote attackers to enumerate users by leveraging the timing difference between responses when a large password is provided.

Technical Details

CVSS Version: 3.1
CNA / NVD Source: [email protected]
Published: 14-Feb-2017 00:59
Last Modified: 17-Jun-2026 07:50
EPSS Date: 2026-11-05
CWE: CWE-200

CVSS Vector


            CVSS:3.1                            AV:N /
                            AC:H /
                            PR:N /
                            UI:N /
                            S:U /
                            C:H /
                            I:N /
                            A:N

CNA Products / Version Status

n/a · n/a Source: CNA · [email protected]
Default status: unknown

n/a — affected

Affected Products / Versions

openbsd / openssh Source: NVD CPE · affected
Version / affected range: * · through (inclusive) 7.2
cpe:2.3:a:openbsd:openssh:*:p2:*:*:*:*:*:*

References

Last enrichment sync: 06-Nov-2026 06:13
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (2)

The salt borrowing comes from a July 15, 2016, OpenSSH change that addressed CVE-2016-6210, a flaw that let attackers learn which usernames exist. Kültekin says the problem has existed since then. OpenSSH 10.6p2 Fixes Critical Long-Password Authentication Bypass on Alpine Linux
However, a patch introduced in OpenSSH in 2016 to fix a username enumeration vulnerability tracked as CVE-2016-6210 changed how OpenSSH handled accounts without usable password hashes. OpenSSH flaw enables logins to password-disabled musl Linux accounts

People (2)

Vendors (2)

Products (7)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.