NetApp Black Box — ONTAP knowledge base

Home / Security / Advisories / NTAP-20190213-0001

NTAP-20190213-0001 — January 2019 OpenSSH Vulnerabilities in NetApp Products

Published 2019-02-13 · Updated 2024-06-14 · Status: Final · Exploitation: Public · Severity: MEDIUM 6.8 · ONTAP affected: Yes

Official advisory: NTAP-20190213-0001 on security.netapp.com ↗. Affected versions, fixed releases, and workarounds live there — this page is a summary.

Product family: Cloud Backup / AltaVault / SteelStore · SolidFire / NetApp HCI · ONTAP  |  ONTAP-relevant  |  highest CVSS: 6.8

CVEs in this advisory

What the CVE records say

CVE-2019-6109 — An issue was discovered in OpenSSH 7.9. Due to missing character encoding in the progress display, a malicious server (or Man-in-The-Middle attacker) can employ crafted object names to manipulate the client output, e.g., by using ANSI control codes to hide additional files being transferred. This affects refresh_progress_meter() in progressmeter.c.

CVE-2019-6110 — 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.

CVE-2019-6111 — An issue was discovered in OpenSSH 7.9. Due to the scp implementation being derived from 1983 rcp, the server chooses which files/directories are sent to the client. However, the scp client only performs cursory validation of the object name returned (only directory traversal attacks are prevented). A malicious scp server (or Man-in-The-Middle attacker) can overwrite arbitrary files in the scp client target directory. If recursive operation (-r) is performed, the server can manipulate subdirectories as well (for example, to overwrite the .ssh/authorized_keys file).

Impact

Successful exploitation of these vulnerabilities could lead to disclosure of sensitive information or the addition or modification of data.

Affected products

Official fixes

References

What to do

  1. Check the affected products listed above against the official advisory's affected-versions table — that is where the exact ONTAP 9 release, ONTAP tool, or management product versions are named.
  2. If affected and a fixed release exists, plan the upgrade — see the ONTAP upgrade runbook.
  3. If exploitation is listed as "active", treat remediation as urgent and review exposure (management LIFs, ONTAP S3, SnapMirror endpoints).
  4. Harden in parallel: security hardening baseline and ransomware protection on ONTAP.

Related reading

Browse all ONTAP CVEs → · Security hub