CVE-2016-0778: The (1) roaming_read and (2) roaming_write functions in roaming_common.c in the client in OpenSSH 5.x, 6.x,...
The (1) roaming_read and (2) roaming_write functions in roaming_common.c in the client in OpenSSH 5.x, 6.x, and 7.x before 7.1p2, when certain proxy and forward options are enabled, do not properly maintain connection file descriptors, which allows remote servers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact by requesting many forwardings.
Security readout for executives and security teams
This is an OpenSSH client flaw, not an SSH server login bypass. A malicious or compromised SSH server could crash a vulnerable client, and the CVE allows for possible broader memory-corruption impact. Business risk is highest for administrators or automation connecting from old OpenSSH clients to untrusted SSH servers. Exposure is limited to systems running vulnerable OpenSSH clients before 7.1p2, especially administrator workstations, jump hosts, build hosts, or automation that initiate outbound SSH sessions. The provided affected-products metadata is incomplete, but vendor advisories show downstream packages from multiple platforms were updated. Treat this as a high-priority legacy client remediation item. It is most urgent where privileged users or automation connect to external SSH servers. It is not described as actively exploited in the provided sources, but old OpenSSH clients should not remain in production. Mitigation focus: Upgrade OpenSSH client packages to 7.1p2 or later vendor-fixed versions.; Apply relevant operating system vendor security updates for OpenSSH.; Disable SSH client roaming where upgrade is delayed, if supported by vendor guidance..
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 · low confidence lookup
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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.
1CVSS vectors
3Timeline events
2ADP providers
11Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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-119 · source CWE mapping
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.