Home / Security / Advisories / NTAP-20160121-0002
NTAP-20160121-0002 — January 2016 MySQL Vulnerabilities in Multiple NetApp Products
Published 2016-01-21 · Updated 2017-01-10 · Status: Final · Exploitation: Public · Severity: not scored · ONTAP affected: Yes
Official advisory: NTAP-20160121-0002 on security.netapp.com ↗. Affected versions, fixed releases, and workarounds live there — this page is a summary.
Product family: OnCommand family · ONTAP | ONTAP-relevant
CVEs in this advisory
- CVE-2016-0546 · site index
- CVE-2016-0504 · site index
- CVE-2016-0505 · site index
- CVE-2016-0594 · site index
- CVE-2016-0595 · site index
- CVE-2016-0503 · site index
- CVE-2016-0596 · site index
- CVE-2016-0502 · site index
- CVE-2016-0597 · site index
- CVE-2016-0611 · site index
- CVE-2016-0616 · site index
- CVE-2016-0598 · site index
- CVE-2016-0600 · site index
- CVE-2016-0610 · site index
- CVE-2016-0599 · site index
- CVE-2016-0601 · site index
- CVE-2016-0606 · site index
- CVE-2016-0608 · site index
- CVE-2016-0607 · site index
- CVE-2015-7744 · site index
- CVE-2016-0605 · site index
- CVE-2016-0609 · site index
Impact
Successful exploitation of these vulnerabilities may lead to the unauthorized ability to takeover MySQL Server, to unauthorized read, update, insert or delete access to a subset of MySQL Server accessible data, or to a hang or frequently repeatable crash (partial or complete DOS) of MySQL Server.
Affected products
- OnCommand Balance
- OnCommand Insight
- OnCommand Performance Manager (Unified Manager Performance Pkg)
- OnCommand Unified Manager for Clustered Data ONTAP
- OnCommand Workflow Automation
Official fixes
- OnCommand Insight — vendor fix ↗
- OnCommand Balance — vendor fix ↗
- OnCommand Unified Manager for Clustered Data ONTAP — vendor fix ↗
- OnCommand Unified Manager for Clustered Data ONTAP — vendor fix ↗
- OnCommand Unified Manager for Clustered Data ONTAP — vendor fix ↗
- OnCommand Workflow Automation — vendor fix ↗
- OnCommand Performance Manager (Unified Manager Performance Pkg) — vendor fix ↗
References
- http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html ↗
- http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html#AppendixMSQL ↗
- http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html#MSQL ↗
- http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0546 ↗
- http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0504 ↗
- http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0505 ↗
- http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0594 ↗
- http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0595 ↗
What to do
- 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.
- If affected and a fixed release exists, plan the upgrade — see the ONTAP upgrade runbook.
- If exploitation is listed as "active", treat remediation as urgent and review exposure (management LIFs, ONTAP S3, SnapMirror endpoints).
- Harden in parallel: security hardening baseline and ransomware protection on ONTAP.
Related reading
- Common ONTAP problems (FAQ) — plain-language symptoms and fixes
- ONTAP security hardening — baseline lockdown guidance
- Ransomware protection on ONTAP — SnapLock, SnapMirror vaulting, Anomaly Detection
- ONTAP error messages index — EMS/WAFL/NFS/SnapMirror messages
- Every NetApp advisory published in 2016