CVE-2016-6210: sshd in OpenSSH before 7.3, when SHA256 or SHA512 are used for user password hashing, uses BLOWFISH hashing...
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.
Security readout for executives and security teams
This OpenSSH issue can let a remote attacker infer whether usernames exist by measuring SSH login response timing. It does not grant access by itself, but it can improve password-guessing or targeting. The sources describe affected OpenSSH before 7.3 under SHA256 or SHA512 password hashing. Internet-facing SSH services running OpenSSH before 7.3 are the primary concern, especially Unix-like systems using SHA256 or SHA512 password hashes. Appliances bundling older OpenSSH may also be exposed if their vendors shipped affected builds. Treat this as a targeted exposure-reduction item, not an emergency breach indicator. Patch older SSH services during normal vulnerability remediation, with higher priority for internet-facing administrative systems and environments with weak account hygiene. Mitigation focus: Upgrade OpenSSH to 7.3 or a vendor-fixed package.; Apply relevant Debian, Red Hat, Gentoo, or product vendor advisories.; Prioritize internet-facing SSH services and administrative jump hosts..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-200 · source CWE mapping
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.