Home / Security / Advisories / NTAP-20230427-0007
NTAP-20230427-0007 — April 2023 MySQL Server Vulnerabilities in NetApp Products
Published 2023-04-27 · Updated 2024-05-17 · 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-37434 — CRITICAL · CVSS 9.8 · site index
- CVE-2022-43548 · site index
- CVE-2022-43551 — HIGH · CVSS 7.5 · site index
- CVE-2023-0215 — HIGH · CVSS 7.5 · site index
- CVE-2023-21911 · site index
- CVE-2023-21912 · site index
- CVE-2023-21913 · site index
- CVE-2023-21917 · site index
- CVE-2023-21919 · site index
- CVE-2023-21920 · site index
- CVE-2023-21929 · site index
- CVE-2023-21933 · site index
- CVE-2023-21935 · site index
- CVE-2023-21940 · site index
- CVE-2023-21945 · site index
- CVE-2023-21946 · site index
- CVE-2023-21947 · site index
- CVE-2023-21953 · site index
- CVE-2023-21955 · site index
- CVE-2023-21962 · site index
- CVE-2023-21963 · site index
- CVE-2023-21966 · site index
- CVE-2023-21971 · site index
- CVE-2023-21972 · site index
- CVE-2023-21976 · site index
- CVE-2023-21977 · site index
- CVE-2023-21980 · site index
- CVE-2023-21982 · site index
What the CVE records say
CVE-2022-37434 — zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).
CVE-2022-43551 — A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) `.`. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.
CVE-2023-0215 — The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected.
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 Workflow Automation — vendor fix ↗
- OnCommand Insight — vendor fix ↗
- SnapCenter — vendor fix ↗
References
- https://www.oracle.com/security-alerts/ ↗
- https://www.oracle.com/security-alerts/cpuapr2023verbose.html#MSQL ↗
- https://www.oracle.com/security-alerts/cpuapr2023.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