LiveActive security incident?Get immediate response
CVE Record

CVE-2019-6110: In OpenSSH 7.9, due to accepting and displaying arbitrary stderr output from the server, a malicious server...

In OpenSSH 7.9, due to accepting and displaying arbitrary stderr output from the server, a malicious server (or Man-in-The-Middle attacker) can manipulate the client output, for example to use ANSI control codes to hide additional files being transferred.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects OpenSSH scp clients that trust and display arbitrary server error output. A malicious server or man-in-the-middle can alter what the user sees, potentially hiding unexpected file transfers. It requires user interaction and a malicious or intercepted connection, so urgency is moderate, not emergency-level.

Executive priority

Prioritize normal vulnerability remediation for developer workstations, admin jump hosts, and automation systems that use scp. Escalate only where users routinely pull files from untrusted servers or sensitive file-transfer workflows depend on scp output for trust decisions.

Technical view

CVE-2019-6110 is an scp client output-manipulation issue in OpenSSH 7.9. The client accepts stderr from the server and displays it, allowing ANSI control sequences to obscure terminal output. The CVSS vector shows network attack, high complexity, no privileges, required user interaction, and high confidentiality and integrity impact.

Likely exposure

Exposure is most likely on systems or workflows using affected OpenSSH scp clients to copy files from servers that may be malicious, compromised, or reachable through interceptable networks. The source bundle does not provide a complete affected version matrix.

Exploitation context

The CVE is not listed as KEV in the provided data, so active exploitation is not established here. A public Exploit-DB reference exists, which indicates public exploit information, but this assessment does not infer current real-world exploitation from that alone.

Researcher notes

The key issue is terminal-output deception, not direct remote code execution. Validation should focus on client behavior, affected OpenSSH packaging, and vendor downstream advisories. Evidence is incomplete for exact affected product scope beyond OpenSSH 7.9 and listed vendor references.

Mitigation direction

  • Apply vendor-provided OpenSSH or platform security updates for CVE-2019-6110.
  • Check NetApp, Gentoo, Siemens, and OS vendor advisories for affected products.
  • Avoid using scp with untrusted or newly provisioned servers until patched.
  • Prefer safer vendor-recommended transfer workflows where available.
  • Treat unexpected scp terminal output or file lists as potentially misleading.

Validation and detection

  • Inventory endpoints and automation using OpenSSH scp clients.
  • Identify OpenSSH 7.9 or vendor-declared affected packages.
  • Review file-transfer workflows involving third-party, temporary, or untrusted servers.
  • Confirm patched package versions through vendor security advisories.
  • Check whether compensating controls reduce man-in-the-middle exposure.
Prepared
Confidence
medium
Sources
9

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-838: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-6110 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
0Timeline events
0ADP providers
8Source links

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.

ScoreVersionSeverityVectorExploitImpactSource
6.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N1.65.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2019-6110Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-838 · source CWE mapping

Inappropriate Encoding for Output Context

Inappropriate Encoding for Output Context represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.