Skip to content
OpenAdvisories

Summary

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Internet Systems Consortium BIND ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.

Product

BIND (Berkeley Internet Name Domain) ist ein Open-Source-Softwarepaket, das einen Domain-Name-System-Server implementiert.

Vulnerabilities 9

  • High 8.6

    DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field

    The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1,…

  • High 7.5

    Potential wildcard CNAME RPZ policy bypass

    An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It…

  • High 7.5

    Unnecessary validation of DNSSEC signed records

    The issue is a resource exhaustion vulnerability associated with DNSSEC validation. BIND always validates all RRSIG records in an answer, even if they are not strictly needed. A query to an authoritative server/zone which returns many valid but superfluous RR…

  • High 7.5

    Potential memory usage beyond configured limits

    A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memory usage c…

  • High 7.5

    Cache poisoning possible with label count discrepancy, RRSIG, and wildcards

    It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is contained. This causes `named` to produce a wildcard name for a zone that is shorter than the attacker's zone, wh…

  • High 7.5

    Record ordering based unexpected exit with CNAME or DNAME

    The issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A records. Specifically, if a client queries for a DNAME and A record below the DNAME to the resolver, and the authoritative …

  • High 7.5

    Unexpected exit in certain situations with NSEC and NSEC3 both present

    If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. This issue affects BIND 9 versions 9.…

  • Medium 6.8

    Incorrect acceptance of NSEC3 records

    BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated NXDOMAIN responses. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through …

  • Medium 6.5

    Key Record using PRIVATEDNS algorithm may lead to unexpected exit

    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 algorith…

Revision history

  1. #34

    Neue Updates von Red Hat aufgenommen

  2. #33

    Neue Updates von Red Hat aufgenommen

  3. #32

    Neue Updates von Oracle Linux aufgenommen

  4. #31

    Neue Updates von Red Hat aufgenommen

  5. #30

    Neue Updates von Oracle Linux aufgenommen

  6. #29

    Neue Updates von F5 und Ubuntu aufgenommen

  7. #28

    Neue Updates von Red Hat aufgenommen

  8. #27

    Neue Updates von Red Hat und Oracle Linux aufgenommen

  9. #26

    Neue Updates von Oracle Linux aufgenommen

  10. #25

    Neue Updates von Red Hat aufgenommen

  11. #24

    Neue Updates von F5 aufgenommen

  12. #23

    Neue Updates von Red Hat aufgenommen

  13. #22

    Neue Updates von IBM aufgenommen

  14. #21

    Neue Updates von Red Hat aufgenommen

  15. #20

    Neue Updates von F5 aufgenommen

  16. #19

    Neue Updates von F5 aufgenommen

  17. #18

    Neue Updates von Red Hat aufgenommen

  18. #17

    Neue Updates von Ubuntu aufgenommen

  19. #16

    Neue Updates von Red Hat aufgenommen

  20. #15

    Neue Updates von Red Hat aufgenommen

  21. #14

    Neue Updates von Red Hat und Ubuntu aufgenommen

  22. #13

    Neue Updates von Oracle Linux aufgenommen

  23. #12

    Neue Updates von Oracle Linux und Rocky Enterprise Software Foundation aufgenommen

  24. #11

    Neue Updates von Red Hat und Rocky Enterprise Software Foundation aufgenommen

  25. #10

    Neue Updates von Rocky Enterprise Software Foundation und Red Hat aufgenommen

References