Home / Security / Advisories / NTAP-20240201-0005

NTAP-20240201-0005 — January 2024 MySQL Cluster Vulnerabilities in NetApp Products

Published 2024-02-01 · Updated 2024-05-23 · Status: Final · Exploitation: Public · Severity: CRITICAL 9.8 · ONTAP affected: No — other NetApp product

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

Product family: Active IQ Unified Manager · Baseboard management controllers · OnCommand family · SnapCenter  |  other NetApp product  |  highest CVSS: 9.8

CVEs in this advisory

What the CVE records say

CVE-2023-28484 — In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c.

CVE-2023-38545 — This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.

Impact

Successful attacks of these vulnerabilities could allow attackers with network access via multiple protocols to compromise MySQL Server.

Affected products

References

What to do

  1. Compare your installed product and version against the affected list above and the official advisory's affected-versions table.
  2. Apply the fixed release named in the official advisory, or the documented workaround if no fix ships yet.
  3. Limit management-plane exposure (BMC/management interfaces, web UIs, SNMP) until patched.
  4. Track follow-ups in the site CVE index and the security RSS feed.

Related reading

Browse all ONTAP CVEs → · Security hub