← Back

Data Ontap Edge

data_ontap_edge

Vendor: Netapp • 23 CVEs

CVEs (23)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
4Debian
IscNetapp+1 more
12Bind
Data Ontap EdgeDebian Linux+9 more
May 6, 2026
Jan 12, 2017
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
named in ISC BIND 9.x before 9.9.9-P5, 9.10.x before 9.10.4-P5, and 9.11.x before 9.11.0-P2 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a malformed response to an RTYPE AN...Show more
named in ISC BIND 9.x before 9.9.9-P5, 9.10.x before 9.10.4-P5, and 9.11.x before 9.11.0-P2 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a malformed response to an RTYPE ANY query.Show less
4Debian
IscNetapp+1 more
11Bind
Data Ontap EdgeDebian Linux+8 more
May 6, 2026
Nov 2, 2016
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
named in ISC BIND 9.x before 9.9.9-P4, 9.10.x before 9.10.4-P4, and 9.11.x before 9.11.0-P1 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a DNAME record in the answer sectio...Show more
named in ISC BIND 9.x before 9.9.9-P4, 9.10.x before 9.10.4-P4, and 9.11.x before 9.11.0-P1 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a DNAME record in the answer section of a response to a recursive query, related to db.c and resolver.c.Show less
2Ietf
Netapp
13Clustered Data Ontap Antivirus Connector
Data Ontap EdgeHost Agent+10 more
May 6, 2026
Sep 21, 2016
N/A· v4
8.1 HIGH· v3
6.8 MEDIUM· v2
The TLS protocol 1.2 and earlier supports the rsa_fixed_dh, dss_fixed_dh, rsa_fixed_ecdh, and ecdsa_fixed_ecdh values for ClientCertificateType but does not directly document the ability to compute the master secret in c...Show more
The TLS protocol 1.2 and earlier supports the rsa_fixed_dh, dss_fixed_dh, rsa_fixed_ecdh, and ecdsa_fixed_ecdh values for ClientCertificateType but does not directly document the ability to compute the master secret in certain situations with a client secret key and server public key but not a server secret key, which makes it easier for man-in-the-middle attackers to spoof TLS servers by leveraging knowledge of the secret key for an arbitrary installed client X.509 certificate, aka the "Key Compromise Impersonation (KCI)" issue.Show less