FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-03-29 07:54:42 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

These are the vulnerabilities relating to the commit you have selected:

VuXML IDDescription
1ecc0d3f-ae8e-11e1-965b-0024e88a8c98dns/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
53a0ddef-0208-11e2-8afa-0024e830109bdns/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


0bc67930-d5c3-11e1-bef6-0024e81297aedns/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
57a700f9-12c0-11e2-9f86-001d923933b6dns/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