What is the severity of CVE-2016-6210?

CVE-2016-6210 is considered a medium severity vulnerability due to the potential for user enumeration attacks.

How do I fix CVE-2016-6210?

To fix CVE-2016-6210, upgrade OpenSSH to version 7.3 or later where SHA256 or SHA512 hashing is implemented correctly.

What systems are affected by CVE-2016-6210?

CVE-2016-6210 affects OpenSSH versions prior to 7.3, particularly version 7.2 and earlier.

Can CVE-2016-6210 lead to a security breach?

Yes, CVE-2016-6210 can lead to a security breach as it allows remote attackers to enumerate valid usernames.

What mitigations are available for CVE-2016-6210?

Mitigations for CVE-2016-6210 include employing additional controls such as account lockouts and using different hashing algorithms.

Vulnerability/
CVE-2016-6210

medium

5.9

CWE

200

18/7/2016

13/2/2017

6/8/2024

CVE-2016-6210: Infoleak

First published: Mon Jul 18 2016(Updated: )

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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
OpenSSH	<=7.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-6210?
CVE-2016-6210 is considered a medium severity vulnerability due to the potential for user enumeration attacks.
How do I fix CVE-2016-6210?
To fix CVE-2016-6210, upgrade OpenSSH to version 7.3 or later where SHA256 or SHA512 hashing is implemented correctly.
What systems are affected by CVE-2016-6210?
CVE-2016-6210 affects OpenSSH versions prior to 7.3, particularly version 7.2 and earlier.
Can CVE-2016-6210 lead to a security breach?
Yes, CVE-2016-6210 can lead to a security breach as it allows remote attackers to enumerate valid usernames.
What mitigations are available for CVE-2016-6210?
Mitigations for CVE-2016-6210 include employing additional controls such as account lockouts and using different hashing algorithms.

agent/type
agent/first-publish-date
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2016-6210
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/weakness
agent/references
agent/author
agent/description
agent/event
agent/source
agent/tags
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
vendor/openbsd
canonical/openssh
version/openssh/7.2

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-6210?
CVE-2016-6210 is considered a medium severity vulnerability due to the potential for user enumeration attacks.
How do I fix CVE-2016-6210?
To fix CVE-2016-6210, upgrade OpenSSH to version 7.3 or later where SHA256 or SHA512 hashing is implemented correctly.
What systems are affected by CVE-2016-6210?
CVE-2016-6210 affects OpenSSH versions prior to 7.3, particularly version 7.2 and earlier.
Can CVE-2016-6210 lead to a security breach?
Yes, CVE-2016-6210 can lead to a security breach as it allows remote attackers to enumerate valid usernames.
What mitigations are available for CVE-2016-6210?
Mitigations for CVE-2016-6210 include employing additional controls such as account lockouts and using different hashing algorithms.