VuXML ID | Description |
53a0ddef-0208-11e2-8afa-0024e830109b | dns/bind9* -- Several vulnerabilities
ISC reports:
Prevents a crash when queried for a record whose RDATA exceeds
65535 bytes.
Prevents a crash when validating caused by using "Bad cache" data
before it has been initialized.
ISC_QUEUE handling for recursive clients was updated to address
a race condition that could cause a memory leak. This rarely
occurred with UDP clients, but could be a significant problem
for a server handling a steady rate of TCP queries.
A condition has been corrected where improper handling of
zero-length RDATA could cause undesirable behavior, including
termination of the named process.
Discovery 2012-09-12 Entry 2012-09-18 bind99
< 9.9.1.3
bind98
< 9.8.3.3
bind97
< 9.7.6.3
bind96
< 9.6.3.1.ESV.R7.3
|
1e1421f0-8d6f-11e0-89b4-001ec9578670 | BIND -- Large RRSIG RRsets and Negative Caching DoS
ISC reports:
A BIND 9 DNS server set up to be a caching resolver is
vulnerable to a user querying a domain with very large resource
record sets (RRSets) when trying to negatively cache a response.
This can cause the BIND 9 DNS server (named process) to crash.
Discovery 2011-05-26 Entry 2011-06-04 Modified 2016-08-09 bind9-sdb-ldap
bind9-sdb-postgresql
< 9.4.3.4
bind96
< 9.6.3.1.ESV.R4.1
bind97
< 9.7.3.1
bind98
< 9.8.0.2
FreeBSD
>= 7.3 lt 7.3_6
>= 7.4 lt 7.4_2
>= 8.1 lt 8.1_4
>= 8.2 lt 8.2_2
CVE-2011-1910
SA-11:02.bind
http://www.isc.org/software/bind/advisories/cve-2011-1910
|
90cc1494-10ac-11e1-b3ec-0024e830109b | BIND -- Remote DOS
The Internet Systems Consortium reports:
Organizations across the Internet reported crashes interrupting
service on BIND 9 nameservers performing recursive queries.
Affected servers crashed after logging an error in query.c with
the following message: "INSIST(! dns_rdataset_isassociated(sigrdataset))"
Multiple versions were reported being affected, including all
currently supported release versions of ISC BIND 9.
Because it may be possible to trigger this bug even on networks
that do not allow untrusted users to access the recursive name
servers (perhaps via specially crafted e-mail messages, and/or
malicious web sites) it is recommended that ALL operators of
recursive name servers upgrade immediately.
Discovery 2011-11-16 Entry 2011-11-16 Modified 2012-01-29 FreeBSD
>= 7.3 lt 7.3_9
>= 7.4 lt 7.4_5
>= 8.1 lt 8.1_7
>= 8.2 lt 8.2_5
bind96
< 9.6.3.1.ESV.R5.1
bind97
< 9.7.4.1
bind98
< 9.8.1.1
SA-11:06.bind
CVE-2011-4313
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4313
https://www.isc.org/software/bind/advisories/cve-2011-4313
|
fd64188d-a71d-11e0-89b4-001ec9578670 | BIND -- Remote DoS against authoritative and recursive servers
ISC reports:
A defect in the affected BIND 9 versions allows an attacker to
remotely cause the "named" process to exit using a specially
crafted packet.
This defect affects both recursive and authoritative servers.
Discovery 2011-07-05 Entry 2011-07-05 bind96
< 9.6.3.1.ESV.R4.3
bind97
< 9.7.3.3
bind98
< 9.8.0.4
CVE-2011-2464
https://www.isc.org/software/bind/advisories/cve-2011-2464
|
0bc67930-d5c3-11e1-bef6-0024e81297ae | dns/bind9* -- Heavy DNSSEC Validation Load Can Cause a 'Bad Cache' Assertion Failure
ISC reports:
High numbers of queries with DNSSEC validation enabled can
cause an assertion failure in named, caused by using a 'bad cache'
data structure before it has been initialized.
BIND 9 stores a cache of query names that are known to be failing due
to misconfigured name servers or a broken chain of trust. Under high query
loads when DNSSEC validation is active, it is possible for a condition
to arise in which data from this cache of failing queries could be used
before it was fully initialized, triggering an assertion failure.
This bug cannot be encountered unless your server is doing DNSSEC
validation.
Discovery 2012-07-24 Entry 2012-07-24 bind99
< 9.9.1.2
bind98
< 9.8.3.2
bind97
< 9.7.6.2
bind96
< 9.6.3.1.ESV.R7.2
CVE-2012-3817
https://kb.isc.org/article/AA-00729
|
1ecc0d3f-ae8e-11e1-965b-0024e88a8c98 | dns/bind9* -- zero-length RDATA can cause named to terminate, reveal memory
ISC reports:
Processing of DNS resource records where the rdata field is zero length
may cause various issues for the servers handling them.
Processing of these records may lead to unexpected outcomes. Recursive
servers may crash or disclose some portion of memory to the client.
Secondary servers may crash on restart after transferring a zone
containing these records. Master servers may corrupt zone data if the
zone option "auto-dnssec" is set to "maintain". Other unexpected
problems that are not listed here may also be encountered.
Impact: This issue primarily affects recursive nameservers.
Authoritative nameservers will only be impacted if an administrator
configures experimental record types with no data. If the server is
configured this way, then secondaries can crash on restart after
transferring that zone. Zone data on the master can become corrupted if
the zone with those records has named configured to manage the DNSSEC
key rotation.
Discovery 2012-06-04 Entry 2012-06-04 Modified 2012-06-06 bind99
< 9.9.1.1
bind98
< 9.8.3.1
bind97
< 9.7.6.1
bind96
< 9.6.3.1.ESV.R7.1
CVE-2012-1667
http://www.isc.org/software/bind/advisories/cve-2012-1667
|
57a700f9-12c0-11e2-9f86-001d923933b6 | dns/bind9* -- crash on deliberately constructed combination of records
ISC reports:
A deliberately constructed combination of records could cause named
to hang while populating the additional section of a response.
Discovery 2012-09-26 Entry 2012-10-10 bind99
< 9.9.1.4
bind99-base
< 9.9.1.4
bind98
< 9.8.3.4
bind98-base
< 9.8.3.4
bind97
< 9.7.6.4
bind97-base
< 9.7.6.4
bind96
< 9.6.3.1.ESV.R7.4
bind96-base
< 9.6.3.1.ESV.R7.4
CVE-2012-5166
|