VYPR

Bind

by Isc

Source repositories

CVEs (228)

  • CVE-2021-25214MedApr 29, 2021
    risk 0.43cvss 6.5epss 0.06

    In BIND 9.8.5 -> 9.8.8, 9.9.3 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.9.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND 9 Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.11 of the BIND 9.17 development branch, when a vulnerable version of…

  • CVE-2020-8622MedAug 21, 2020
    risk 0.43cvss 6.5epss 0.06

    In BIND 9.0.0 -> 9.11.21, 9.12.0 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.9.3-S1 -> 9.11.21-S1 of the BIND 9 Supported Preview Edition, An attacker on the network path for a TSIG-signed request, or operating the server receiving the TSIG-signed request, could send a truncated…

  • CVE-2018-5741MedJan 16, 2019
    risk 0.43cvss 6.5epss 0.03

    To provide fine-grained controls over the ability to use Dynamic DNS (DDNS) to update records in a zone, BIND 9 provides a feature called update-policy. Various rules can be configured to limit the types of updates that can be performed by a client, depending on the key used…

  • CVE-2017-3138MedJan 16, 2019
    risk 0.43cvss 6.5epss 0.06

    named contains a feature which allows operators to issue commands to a running server by communicating with the server process over a control channel, using a utility program such as rndc. A regression introduced in a recent feature change has created a situation under which…

  • CVE-2016-2775MedJul 19, 2016
    risk 0.43cvss 5.9epss 0.63

    ISC BIND 9.x before 9.9.9-P2, 9.10.x before 9.10.4-P2, and 9.11.x before 9.11.0b2, when lwresd or the named lwres option is enabled, allows remote attackers to cause a denial of service (daemon crash) via a long request that uses the lightweight resolver protocol.

  • CVE-2026-19033MedSep 16, 2026
    risk 0.42cvss 6.5epss 0.00

    For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send…

  • CVE-2026-10822MedJul 22, 2026
    risk 0.42cvss 6.5epss 0.00

    If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit. BIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS algorithm (253), and in the…

  • CVE-2026-5946HigMay 20, 2026
    risk 0.42cvss 7.5epss 0.02

    Multiple flaws have been identified in `named` related to the handling of DNS messages whose CLASS is not Internet (`IN`) — for example, `CHAOS` or `HESIOD`, or DNS messages that specify meta-classes (`ANY` or `NONE`) in the question section. Specially crafted requests…

  • CVE-2026-3039HigMay 20, 2026
    risk 0.42cvss 7.5epss 0.01

    BIND servers that are configured to use TKEY-based authentication via GSS-API tokens are vulnerable to excessive memory consumption when receiving and processing maliciously-constructed packets. Typically these servers will be found in Active Directory integrated DNS…

  • CVE-2026-3119MedMar 25, 2026
    risk 0.42cvss 6.5epss 0.01

    Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record. The affected code can only be reached if an incoming request has a valid transaction signature (TSIG) from a key declared in the `named` configuration. This issue…

  • CVE-2026-1519HigMar 25, 2026
    risk 0.42cvss 7.5epss 0.02

    If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume excessive CPU. Authoritative-only servers are generally unaffected, although there are circumstances where authoritative servers may make recursive queries…

  • CVE-2013-5661MedNov 5, 2019
    risk 0.39cvss 5.9epss 0.03

    Cache Poisoning issue exists in DNS Response Rate Limiting.

  • CVE-2019-6476MedOct 17, 2019
    risk 0.39cvss 5.9epss 0.03

    A defect in code added to support QNAME minimization can cause named to exit with an assertion failure if a forwarder returns a referral rather than resolving the query. This affects BIND versions 9.14.0 up to 9.14.6, and 9.15.0 up to 9.15.4.

  • CVE-2019-6471MedOct 9, 2019
    risk 0.39cvss 5.9epss 0.03

    A race condition which may occur when discarding malformed packets can result in BIND exiting due to a REQUIRE assertion failure in dispatch.c. Versions affected: BIND 9.11.0 -> 9.11.7, 9.12.0 -> 9.12.4-P1, 9.14.0 -> 9.14.2. Also all releases of the BIND 9.13 development branch…

  • CVE-2018-5737MedJan 16, 2019
    risk 0.39cvss 5.9epss 0.11

    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…

  • CVE-2017-3136MedJan 16, 2019
    risk 0.39cvss 5.9epss 0.11

    A query with a specific set of characteristics could cause a server using DNS64 to encounter an assertion failure and terminate. An attacker could deliberately construct a query, enabling denial-of-service against a server if it was configured to use the DNS64 feature and other…

  • CVE-2016-1284MedFeb 4, 2016
    risk 0.39cvss 5.9epss 0.03

    rdataset.c in ISC BIND 9 Supported Preview Edition 9.9.8-S before 9.9.8-S5, when nxdomain-redirect is enabled, allows remote attackers to cause a denial of service (REQUIRE assertion failure and daemon exit) via crafted flag values in a query.

  • CVE-2026-77119MedSep 16, 2026
    risk 0.38cvss 5.9epss 0.00

    A validly signed NSEC3 from an unrelated sibling zone may be accepted as an insecurity proof, downgrading a secure delegation and letting a forged unsigned answer through. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25,…

  • CVE-2026-78301MedSep 16, 2026
    risk 0.38cvss 5.8epss 0.00

    A malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose authoritative status…

  • CVE-2026-19941MedSep 16, 2026
    risk 0.38cvss 5.9epss 0.00

    An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record. This issue affects BIND 9 versions 9.11.0…

Page 6 of 12