Home / Security / Advisories / NTAP-20180926-0004

NTAP-20180926-0004 — May 2018 ISC BIND Vulnerabilities in NetApp Products

Published 2018-09-26 · Updated 2019-07-10 · Status: Final · Exploitation: Public · Severity: MEDIUM 5.9 · ONTAP affected: Yes

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

Product family: ONTAP · Cloud Backup / AltaVault / SteelStore | ONTAP-relevant | highest CVSS: 5.9

CVEs in this advisory

CVE-2018-5736 — MEDIUM · CVSS 5.3 · site index
CVE-2018-5737 — MEDIUM · CVSS 5.9 · site index

What the CVE records say

CVE-2018-5736 — An error in zone database reference counting can lead to an assertion failure if a server which is running an affected version of BIND attempts several transfers of a slave zone in quick succession. This defect could be deliberately exercised by an attacker who is permitted to cause a vulnerable server to initiate zone transfers (for example: by sending valid NOTIFY messages), causing the named process to exit after failing the assertion test. Affects BIND 9.12.0 and 9.12.1.

CVE-2018-5737 — A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is off. Additionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cases cause undesirable behavior from named, such as a recursion loop or excessive logging. Deliberate exploitation of this condition could cause operational problems depending on the particular manifestation -- either degradation or denial of service. Affects BIND 9.12.0 and 9.12.1.

Impact

Successful exploitation of these vulnerabilities could lead to Denial of Service (DoS).

Affected products

Data ONTAP Edge
NetApp Cloud Backup (formerly AltaVault)

Official fixes

NetApp Cloud Backup (formerly AltaVault) — vendor fix ↗

References

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.