FreshPorts - VuXML

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.

< 9.9.1.2

< 9.8.3.2

< 9.7.6.2

< 9.6.3.1.ESV.R7.2

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.

< 9.4.3.4

< 9.6.3.1.ESV.R4.1

< 9.7.3.1

< 9.8.0.2

ge 7.3 lt 7.3_6

ge 7.4 lt 7.4_2

ge 8.1 lt 8.1_4

ge 8.2 lt 8.2_2

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.

< 9.9.1.1

< 9.8.3.1

< 9.7.6.1

< 9.6.3.1.ESV.R7.1

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.

< 9.9.2.1

< 9.9.2.1

< 9.8.4.1

< 9.8.4.1

ISC reports:

Two defects were discovered in ISC's BIND 9.8 code. These defects only affect BIND 9.8 servers which have recursion enabled and which use a specific feature of the software known as Response Policy Zones (RPZ) and where the RPZ zone contains a specific rule/action pattern.

< 9.8.0.4

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.

< 9.9.1.3

< 9.8.3.3

< 9.7.6.3

< 9.6.3.1.ESV.R7.3

ISC reports:

A deliberately constructed combination of records could cause named to hang while populating the additional section of a response.

< 9.9.1.4

< 9.9.1.4

< 9.8.3.4

< 9.8.3.4

< 9.7.6.4

< 9.7.6.4

< 9.6.3.1.ESV.R7.4

< 9.6.3.1.ESV.R7.4

ISC reports:

A bug has been discovered in the most recent releases of BIND 9 which has the potential for deliberate exploitation as a denial-of-service attack. By sending a recursive resolver a query for a record in a specially malformed zone, an attacker can cause BIND 9 to exit with a fatal "RUNTIME_CHECK" error in resolver.c.

gt 9.9.3 lt 9.9.3.1

gt 9.9.3 lt 9.9.3.1

gt 9.8.5 lt 9.8.5.1

gt 9.8.5 lt 9.8.5.1

gt 9.6.3.1.ESV.R9 lt 9.6.3.2.ESV.R9

gt 9.6.3.1.ESV.R9 lt 9.6.3.2.ESV.R9

ISC reports:

A specially crafted query that includes malformed rdata can cause named to terminate with an assertion failure while rejecting the malformed query.

gt 9.9.3 lt 9.9.3.2

gt 9.9.3 lt 9.9.3.2

gt 9.8.5 lt 9.8.5.2

gt 9.8.5 lt 9.8.5.2

ge 9.0 lt 9.1_5

ge 8.4 lt 8.4_2

ISC reports:

A critical defect in BIND 9 allows an attacker to cause excessive memory consumption in named or other programs linked to libdns.

< 9.9.2.2

< 9.9.2.2

< 9.8.4.2

< 9.8.4.2

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.

ge 7.3 lt 7.3_9

ge 7.4 lt 7.4_5

ge 8.1 lt 8.1_7

ge 8.2 lt 8.2_5

< 9.6.3.1.ESV.R5.1

< 9.7.4.1

< 9.8.1.1

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]

< 9.9.6

gt 0

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

ISC reports:

An error parsing input received by the rndc control channel can cause an assertion failure in sexpr.c or alist.c.

le 9.8.8

ge 9.9.0 lt 9.9.8P4

ge 9.10.0 lt 9.10.3P4

< 9.11.0.a20160309

ge 9.3 lt 9.3_38

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.

< 9.9.4.2

< 9.9.4.2

< 9.8.6.2

< 9.8.6.2

< 9.6.3.2.ESV.R10.2

< 9.6.3.2.ESV.R10.2

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

ISC reports:

A problem parsing resource record signatures for DNAME resource records can lead to an assertion failure in resolver.c or db.c

le 9.8.8

ge 9.9.0 lt 9.9.8P4

ge 9.10.0 lt 9.10.3P4

< 9.11.0.a20160309

ge 9.3 lt 9.3_38

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.

< 9.6.3.1.ESV.R4.3

< 9.7.3.3

< 9.8.0.4