VuXML ID | Description |
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
|
c93533a3-24f1-11e5-8b74-3c970e169bc2 | bind -- denial of service vulnerability
ISC reports:
A very uncommon combination of zone data has been found
that triggers a bug in BIND, with the result that named
will exit with a "REQUIRE" failure in name.c when validating
the data returned in answer to a recursive query.
A recursive resolver that is performing DNSSEC validation
can be deliberately terminated by any attacker who can
cause a query to be performed against a maliciously
constructed zone. This will result in a denial of
service to clients who rely on that resolver.
Discovery 2015-07-07 Entry 2015-07-07 Modified 2016-08-09 bind910
< 9.10.2P2
bind99
< 9.9.7P1
bind910-base
bind99-base
gt 0
FreeBSD
ge 9.3 lt 9.3_19
ge 8.4 lt 8.4_33
SA-15:11.bind
CVE-2015-4620
https://kb.isc.org/article/AA-01267/
|
c6861494-1ffb-11e7-934d-d05099c0ae8c | BIND -- multiple vulnerabilities
ISC reports:
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
preconditions were met.
Mistaken assumptions about the ordering of records in
the answer section of a response containing CNAME or
DNAME resource records could lead to a situation in
which named would exit with an assertion failure when
processing a response in which records occurred in an
unusual order.
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 some versions of
named can be caused to exit with a REQUIRE assertion
failure if they are sent a null command string.
Discovery 2017-04-12 Entry 2017-04-13 Modified 2017-04-13 bind99
< 9.9.9P8
bind910
< 9.10.4P8
bind911
< 9.11.0P5
bind9-devel
le 9.12.0.a.2017.03.25
CVE-2017-3136
CVE-2017-3137
CVE-2017-3138
https://kb.isc.org/article/AA-01465/0
https://kb.isc.org/article/AA-01466/0
https://kb.isc.org/article/AA-01471/0
|
58033a95-bba8-11e4-88ae-d050992ecde8 | bind -- denial of service vulnerability
ISC reports:
When configured to perform DNSSEC validation, named can
crash when encountering a rare set of conditions in the
managed trust anchors.
Discovery 2015-02-18 Entry 2015-02-23 Modified 2016-08-09 bind910
bind910-base
< 9.10.1P2
bind99
bind99-base
< 9.9.6P2
FreeBSD
ge 9.3 lt 9.3_10
ge 8.4 lt 8.4_24
SA-15:05.bind
CVE-2015-1349
https://kb.isc.org/article/AA-01235
|
d4c7e9a9-d893-11e6-9b4d-d050996490d0 | BIND -- multiple vulnerabilities
ISC reports:
A malformed query response received by a recursive
server in response to a query of RTYPE ANY could
trigger an assertion failure while named is attempting
to add the RRs in the query response to the cache.
Depending on the type of query and the EDNS options
in the query they receive, DNSSEC-enabled authoritative
servers are expected to include RRSIG and other RRsets
in their responses to recursive servers.
DNSSEC-validating servers will also make specific queries
for DS and other RRsets.
Whether DNSSEC-validating or not, an error in processing
malformed query responses that contain DNSSEC-related
RRsets that are inconsistent with other RRsets in the
same query response can trigger an assertion failure.
Although the combination of properties which triggers
the assertion should not occur in normal traffic, it
is potentially possible for the assertion to be triggered
deliberately by an attacker sending a specially-constructed
answer.
An unusually-formed answer containing a DS resource
record could trigger an assertion failure. While the
combination of properties which triggers the assertion
should not occur in normal traffic, it is potentially
possible for the assertion to be triggered deliberately
by an attacker sending a specially-constructed answer
having the required properties.
An error in handling certain queries can cause an
assertion failure when a server is using the
nxdomain-redirect feature to cover a zone for which
it is also providing authoritative service.
A vulnerable server could be intentionally stopped
by an attacker if it was using a configuration that
met the criteria for the vulnerability and if the
attacker could cause it to accept a query that
possessed the required attributes.
Discovery 2017-01-11 Entry 2017-01-12 bind99
< 9.9.9P5
bind910
< 9.10.4P5
bind911
< 9.11.0P2
bind9-devel
le 9.12.0.a.2016.12.28
FreeBSD
ge 9.3 lt 10.0
CVE-2016-9131
CVE-2016-9147
CVE-2016-9444
CVE-2016-9778
https://kb.isc.org/article/AA-01439/0
https://kb.isc.org/article/AA-01440/0
https://kb.isc.org/article/AA-01441/0
https://kb.isc.org/article/AA-01442/0
|
7a31e0de-5b6d-11e6-b334-002590263bf5 | bind -- denial of service vulnerability
ISC reports:
A query name which is too long can cause a segmentation fault in
lwresd.
Discovery 2016-07-18 Entry 2016-08-06 bind99
< 9.9.9P2
bind910
< 9.10.4P2
bind911
< 9.11.0.b2
bind9-devel
< 9.12.0.a.2016.07.14
CVE-2016-2775
https://kb.isc.org/article/AA-01393
|
a8ec4db7-a398-11e5-85e9-14dae9d210b8 | bind -- multiple vulnerabilities
ISC reports:
Named is potentially vulnerable to the OpenSSL vulnerability described in CVE-2015-3193.
Incorrect reference counting could result in an INSIST
failure if a socket error occurred while performing a lookup. This flaw
is disclosed in CVE-2015-8461. [RT#40945]
Insufficient testing when parsing a message allowed records
with an incorrect class to be be accepted, triggering a REQUIRE failure
when those records were subsequently cached. This flaw is disclosed in
CVE-2015-8000. [RT #40987]
Discovery 2015-11-24 Entry 2015-12-16 Modified 2016-08-09 bind99
< 9.9.8P2
bind910
< 9.10.3P2
bind9-devel
< 9.11.0.a20151215
FreeBSD
ge 9.3 lt 9.3_32
https://kb.isc.org/article/AA-01328/0/BIND-9.10.3-P2-Release-Notes.html
https://kb.isc.org/article/AA-01317/0/CVE-2015-8000%3A-Responses-with-a-malformed-class-attribute-can-trigger-an-assertion-failure-in-db.c.html
https://kb.isc.org/article/AA-01319/0/CVE-2015-8461%3A-A-race-condition-when-handling-socket-errors-can-lead-to-an-assertion-failure-in-resolver.c.html
CVE-2015-3193
CVE-2015-8000
CVE-2015-8461
SA-15:27.bind
|
0b8d01a4-a0d2-11e6-9ca2-d050996490d0 | BIND -- Remote Denial of Service vulnerability
ISC reports:
A defect in BIND's handling of responses containing
a DNAME answer can cause a resolver to exit after
encountering an assertion failure in db.c or
resolver.c
Discovery 2016-11-01 Entry 2016-11-02 bind99
< 9.9.9P4
bind910
< 9.10.4P4
bind911
< 9.11.0P1
bind9-devel
le 9.12.0.a.2016.10.21
FreeBSD
ge 9.3 lt 9.3_50
CVE-2016-8864
SA-16:34.bind
https://kb.isc.org/article/AA-01434/
|
c8d902b1-8550-11e6-81e7-d050996490d0 | BIND -- Remote Denial of Service vulnerability
ISC reports:
Testing by ISC has uncovered a critical error condition
which can occur when a nameserver is constructing a
response. A defect in the rendering of messages into
packets can cause named to exit with an assertion
failure in buffer.c while constructing a response
to a query that meets certain criteria.
Discovery 2016-09-27 Entry 2016-09-28 Modified 2016-10-10 bind99
< 9.9.9P3
bind910
< 9.10.4P3
bind911
< 9.11.0.rc3
bind9-devel
< 9.12.0.a.2016.09.10
FreeBSD
ge 9.3 lt 9.3_48
CVE-2016-2776
SA-16:28.bind
https://kb.isc.org/article/AA-01419
|
cb252f01-7c43-11e3-b0a6-005056a37f68 | bind -- denial of service vulnerability
ISC reports:
Because of a defect in handling queries for NSEC3-signed zones,
BIND can crash with an "INSIST" failure in name.c when processing
queries possessing certain properties. By exploiting this defect
an attacker deliberately constructing a query with the right
properties could achieve denial of service against an authoritative
nameserver serving NSEC3-signed zones.
Discovery 2014-01-08 Entry 2014-01-13 Modified 2016-08-09 bind99
< 9.9.4.2
bind99-base
< 9.9.4.2
bind98
< 9.8.6.2
bind98-base
< 9.8.6.2
bind96
< 9.6.3.2.ESV.R10.2
bind96-base
< 9.6.3.2.ESV.R10.2
FreeBSD
ge 9.2 lt 9.2_3
ge 9.1 lt 9.1_10
ge 8.4 lt 8.4_7
ge 8.3 lt 8.3_14
CVE-2014-0591
SA-14:04.bind
https://kb.isc.org/article/AA-01078/74/
|
ab3e98d9-8175-11e4-907d-d050992ecde8 | bind -- denial of service vulnerability
ISC reports:
We have today posted updated versions of 9.9.6 and 9.10.1
to address a significant security vulnerability in DNS
resolution. The flaw was discovered by Florian Maury of
ANSSI, and applies to any recursive resolver that does not
support a limit on the number of recursions. [CERTFR-2014-AVI-512],
[USCERT VU#264212]
A flaw in delegation handling could be exploited to put named
into an infinite loop, in which each lookup of a name server
triggered additional lookups of more name servers. This has
been addressed by placing limits on the number of levels of
recursion named will allow (default 7), and on the number of
queries that it will send before terminating a recursive query
(default 50). The recursion depth limit is configured via the
max-recursion-depth option, and the query limit via the
max-recursion-queries option. For more information, see the
security advisory at https://kb.isc.org/article/AA-01216/.
[CVE-2014-8500]
[RT #37580]
In addition, we have also corrected a potential security
vulnerability in the GeoIP feature in the 9.10.1 release only.
For more information on this issue, see the security advisory
at https://kb.isc.org/article/AA-01217.
[CVE-2014-8680]
Discovery 2014-12-08 Entry 2014-12-11 Modified 2016-08-09 bind99
bind99-base
< 9.9.6
bind98
bind98-base
bind96
bind96-base
gt 0
FreeBSD
ge 9.3 lt 9.3_6
ge 9.2 lt 9.2_16
ge 9.1 lt 9.1_23
ge 8.4 lt 8.4_20
SA-14:29.bind
CVE-2014-8500
CVE-2014-8680
https://www.isc.org/blogs/important-security-advisory-posted/
|
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
|
7a282e49-95b6-11e2-8433-0800273fe665 | dns/bind9* -- Malicious Regex Can Cause Memory Exhaustion
ISC reports:
A critical defect in BIND 9 allows an attacker to cause
excessive memory consumption in named or other programs
linked to libdns.
Discovery 2013-03-11 Entry 2013-03-27 bind99
< 9.9.2.2
bind99-base
< 9.9.2.2
bind98
< 9.8.4.2
bind98-base
< 9.8.4.2
CVE-2013-2266
|
731cdeaa-3564-11e5-9970-14dae9d210b8 | bind -- denial of service vulnerability
ISC reports:
An error in the handling of TKEY queries can be exploited
by an attacker for use as a denial-of-service vector, as a constructed
packet can use the defect to trigger a REQUIRE assertion failure,
causing BIND to exit.
Discovery 2015-07-21 Entry 2015-07-28 Modified 2016-08-09 bind910
< 9.10.2P3
bind99
< 9.9.7P2
bind910-base
bind99-base
gt 0
FreeBSD
ge 9.3 lt 9.3_21
ge 8.4 lt 8.4_35
SA-15:17.bind
CVE-2015-5477
https://kb.isc.org/article/AA-01272/
|
b4578647-c12b-11e5-96d6-14dae9d210b8 | bind -- denial of service vulnerability
ISC reports:
Specific APL data could trigger an INSIST in apl_42.c
Discovery 2016-01-19 Entry 2016-01-22 Modified 2016-08-09 bind99
< 9.9.8P3
bind910
< 9.10.3P3
FreeBSD
ge 9.3 lt 9.3_35
https://kb.isc.org/article/AA-01335
CVE-2015-8704
SA-16:08.bind
|
2892a8e2-3d68-11e2-8e01-0800273fe665 | dns/bind9* -- servers using DNS64 can be crashed by a crafted query
ISC reports:
BIND 9 nameservers using the DNS64 IPv6 transition mechanism are
vulnerable to a software defect that allows a crafted query to
crash the server with a REQUIRE assertion failure. Remote
exploitation of this defect can be achieved without extensive
effort, resulting in a denial-of-service (DoS) vector against
affected servers.
Discovery 2012-11-27 Entry 2012-12-04 bind99
< 9.9.2.1
bind99-base
< 9.9.2.1
bind98
< 9.8.4.1
bind98-base
< 9.8.4.1
CVE-2012-5688
|
eaf3b255-5245-11e5-9ad8-14dae9d210b8 | bind -- denial of service vulnerability
ISC reports:
Parsing a malformed DNSSEC key can cause a validating
resolver to exit due to a failed assertion in buffer.c. It is possible
for a remote attacker to deliberately trigger this condition, for
example by using a query which requires a response from a zone
containing a deliberately malformed key.
Discovery 2015-08-19 Entry 2015-09-03 Modified 2016-08-09 bind99
< 9.9.7P3
bind910
ge 9.10.2 lt 9.10.2P4
bind910-base
bind99-base
gt 0
FreeBSD
ge 9.3 lt 9.3_25
https://www.isc.org/blogs/cve-2015-5722-parsing-malformed-keys-may-cause-bind-to-exit-due-to-a-failed-assertion-in-buffer-c/
CVE-2015-5722
SA-15:23.bind
|
7d08e608-5e95-11e6-b334-002590263bf5 | BIND,Knot,NSD,PowerDNS -- denial over service via oversized zone transfers
ISC reports:
DNS protocols were designed with the assumption that a certain
amount of trust could be presumed between the operators of primary
and secondary servers for a given zone. However, in current
practice some organizations have scenarios which require them to
accept zone data from sources that are not fully trusted (for
example: providers of secondary name service). A party who is
allowed to feed data into a zone (e.g. by AXFR, IXFR, or Dynamic DNS
updates) can overwhelm the server which is accepting data by
intentionally or accidentally exhausting that server's memory.
Discovery 2016-07-06 Entry 2016-08-10 Modified 2017-04-24 bind99
le 9.9.9P2
bind910
le 9.10.4P2
bind911
le 9.11.0.b2
bind9-devel
le 9.12.0.a.2016.11.02
knot
knot1
< 1.6.8
knot2
< 2.3.0
nsd
< 4.1.11
powerdns
< 4.0.1
CVE-2016-6170
CVE-2016-6171
CVE-2016-6172
CVE-2016-6173
https://kb.isc.org/article/AA-01390
http://www.openwall.com/lists/oss-security/2016/07/06/4
|
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
|