Home / Security / Advisories / NTAP-20190301-0001

NTAP-20190301-0001 — CVE-2019-1559 OpenSSL Vulnerability in NetApp Products

Published 2019-03-01 · Updated 2024-01-02 · Status: Final · Exploitation: Public · Severity: MEDIUM 5.9 · ONTAP affected: Yes

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

Product family: Active IQ Unified Manager · Other NetApp products · Baseboard management controllers · Cloud Backup / AltaVault / SteelStore · SolidFire / NetApp HCI · E-Series / SANtricity · ONTAP · OnCommand family · SnapManager / Snap utilities · StorageGRID  |  ONTAP-relevant  |  highest CVSS: 5.9

CVEs in this advisory

What the CVE records say

CVE-2019-1559 — If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this to be exploitable "non-stitched" ciphersuites must be in use. Stitched ciphersuites are optimised implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q).

Impact

Successful exploitation of this vulnerability could lead to disclosure of sensitive information.

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