Home / Security / Advisories / NTAP-20230208-0002
NTAP-20230208-0002 — January 2023 MySQL Server Vulnerabilities in NetApp Products
Published 2023-02-08 · Updated 2024-07-19 · Status: Final · Exploitation: Public · Severity: CRITICAL 9.8 · ONTAP affected: No — other NetApp product
Product family: Active IQ Unified Manager · OnCommand family · SnapCenter | other NetApp product | highest CVSS: 9.8
CVEs in this advisory
- CVE-2022-32221 — CRITICAL · CVSS 9.8 · site index
- CVE-2023-21836 · site index
- CVE-2023-21840 · site index
- CVE-2023-21860 · site index
- CVE-2023-21863 · site index
- CVE-2023-21864 · site index
- CVE-2023-21865 · site index
- CVE-2023-21866 · site index
- CVE-2023-21867 · site index
- CVE-2023-21868 · site index
- CVE-2023-21869 · site index
- CVE-2023-21870 · site index
- CVE-2023-21871 · site index
- CVE-2023-21872 · site index
- CVE-2023-21873 · site index
- CVE-2023-21874 · site index
- CVE-2023-21875 · site index
- CVE-2023-21876 · site index
- CVE-2023-21877 · site index
- CVE-2023-21878 · site index
- CVE-2023-21879 · site index
- CVE-2023-21880 · site index
- CVE-2023-21881 · site index
- CVE-2023-21882 · site index
- CVE-2023-21883 · site index
- CVE-2023-21887 · site index
What the CVE records say
CVE-2022-32221 — When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was used to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent `POST` request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.
Impact
Successful exploitation of these vulnerabilities may lead to unauthorized takeover of MySQL Server, unauthorized read or modification access to a subset or all of the MySQL Server accessible data, or to a hang or frequently repeatable crash (partial or complete DoS) of MySQL Server.
Affected products
- Active IQ Unified Manager for Microsoft Windows
- Active IQ Unified Manager for VMware vSphere
- OnCommand Insight
- OnCommand Workflow Automation
- SnapCenter
Official fixes
- Active IQ Unified Manager for Microsoft Windows — vendor fix ↗
- Active IQ Unified Manager for VMware vSphere — vendor fix ↗
- OnCommand Insight — vendor fix ↗
- OnCommand Workflow Automation — vendor fix ↗
- SnapCenter — vendor fix ↗
References
- https://www.oracle.com/security-alerts/ ↗
- https://www.oracle.com/security-alerts/cpujan2023verbose.html#MSQL ↗
- https://www.oracle.com/security-alerts/cpujan2023.html#AppendixMSQL ↗
What to do
- Compare your installed product and version against the affected list above and the official advisory's affected-versions table.
- Apply the fixed release named in the official advisory, or the documented workaround if no fix ships yet.
- Limit management-plane exposure (BMC/management interfaces, web UIs, SNMP) until patched.
- Track follow-ups in the site CVE index and the security RSS feed.
Related reading
- Site CVE index — every CVE we track, split by year
- Security hub — recent NetApp advisories and what changed
- Security hardening baseline — applies to NetApp management planes generally
- Every NetApp advisory published in 2023