CVE-2016-0778

Public on

Last Modified: UTC

Description

A buffer overflow flaw was found in the way the OpenSSH client roaming feature was implemented. A malicious server could potentially use this flaw to execute arbitrary code on a successfully authenticated OpenSSH client if that client used certain non-default configuration options.

A buffer overflow flaw was found in the way the OpenSSH client roaming feature was implemented. A malicious server could potentially use this flaw to execute arbitrary code on a successfully authenticated OpenSSH client if that client used certain non-default configuration options.

Additional information

  • Bugzilla 1298033: OpenSSH: Client buffer-overflow when using roaming connections
  • CWE-122: Heap-based Buffer Overflow
  • FAQ: Frequently asked questions about CVE-2016-0778

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).

CVSS v2 Score Breakdown
Red HatNVD

CVSS v2 Base Score

5.1

4.6

Attack Vector

Network

Network

Access Complexity

High

High

Authentication

None

Single

Confidentiality Impact

Partial

Partial

Integrity Impact

Partial

Partial

Availability Impact

Partial

Partial

CVSS v2 Vector

Red Hat: AV:N/AC:H/Au:N/C:P/I:P/A:P

NVD: AV:N/AC:H/Au:S/C:P/I:P/A:P

Acknowledgements

Red Hat would like to thank Qualys for reporting this issue.

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?

Want to get errata notifications? Sign up here.