bind vulnerabilities (Azure Linux)
69 vulnerabilities.
bindAzure LinuxEnabling both DNS64 and serve-stale may cause an assertion failure during recursive resolution7.5 HighbindAzure LinuxQuerying RFC 1918 reverse zones may cause an assertion failure when "nxdomain-redirect" is enabled7.5 HighbindAzure LinuxCertain DNSSEC aspects of the DNS protocol (in RFC 4035 and related RFCs) allow remote attackers...7.5 HighbindAzure LinuxParsing large DNS messages may cause excessive CPU load7.5 HighbindAzure LinuxA stack exhaustion flaw in control channel code may cause named to terminate unexpectedly7.5 HighbindAzure LinuxMalformed NSEC records can cause named to terminate unexpectedly when synth-from-dnssec is enabled7.5 HighbindAzure LinuxExceeding the recursive-clients quota may cause named to terminate unexpectedly when stale-answer-client-timeout is set to 07.5 HighbindAzure Linuxnamed's configured cache size limit can be significantly exceeded7.5 HighbindAzure Linuxnamed configured to answer from stale cache may terminate unexpectedly at recursive-clients soft quota7.5 HighbindAzure Linuxnamed configured to answer from stale cache may terminate unexpectedly while processing RRSIG queries7.5 HighbindAzure LinuxAn UPDATE message flood may cause named to exhaust all available memory7.5 HighbindAzure LinuxMemory leaks in EdDSA DNSSEC verification code7.5 HighbindAzure LinuxMemory leak in ECDSA DNSSEC verification code7.5 HighbindAzure LinuxBIND 9 resolvers configured to answer from stale cache with zero stale-answer-client-timeout may terminate unexpectedly7.5 HighbindAzure LinuxProcessing large delegations may severely degrade resolver performance5.3 MediumbindAzure LinuxDoS from specifically crafted TCP packets5.3 MediumbindAzure LinuxDNS forwarders - cache poisoning vulnerability6.8 MediumbindAzure LinuxLame cache can be abused to severely degrade resolver performance5.3 MediumbindAzure Linuxdhcpd: use-after-free error leads crash in IPv6 mode when using mismatched BIND libraries6.5 Medium