CVE-2016-6210
Public on
Last Modified:
Description
A covert timing channel flaw was found in the way OpenSSH handled authentication of non-existent users. A remote unauthenticated attacker could possibly use this flaw to determine valid user names by measuring the timing of server responses.
Statement
This issue in OpenSSH is mitigated by the usage of SELinux in Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7.
Additional information
- Bugzilla 1357442: openssh: User enumeration via covert timing channel
- CWE-385: Covert Timing Channel
- FAQ: Frequently asked questions about CVE-2016-6210
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
| Red Hat | NVD | |
|---|---|---|
CVSS v3 Base Score | 5.3 | 5.9 |
Attack Vector | Network | Network |
Attack Complexity | Low | High |
Privileges Required | None | None |
User Interaction | None | None |
Scope | Unchanged | Unchanged |
Confidentiality Impact | Low | High |
Integrity Impact | None | None |
Availability Impact | None | None |
CVSS v3 Vector
Red Hat: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
| Red Hat | NVD | |
|---|---|---|
CVSS v2 Base Score | 5 | 4.3 |
Attack Vector | Network | Network |
Access Complexity | Low | Medium |
Authentication | None | None |
Confidentiality Impact | Partial | Partial |
Integrity Impact | None | None |
Availability Impact | None | None |
CVSS v2 Vector
Red Hat: AV:N/AC:L/Au:N/C:P/I:N/A:N
NVD: AV:N/AC:M/Au:N/C:P/I:N/A:N
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
What can I do if my product is listed as "Will not fix"?
What can I do if my product is listed as "Fix deferred"?
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
