FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-04-29 10:45:39 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

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

VuXML ID	Description
21a854cc-cac1-11ee-b7a7-353f1e043d9a	DNSSEC validators -- denial-of-service/CPU exhaustion from KeyTrap and NSEC3 vulnerabilities Simon Kelley reports: If DNSSEC validation is enabled, then an attacker who can force a DNS server to validate a specially crafted signed domain can use a lot of CPU in the validator. This only affects dnsmasq installations with DNSSEC enabled. Stichting NLnet Labs reports: The KeyTrap [CVE-2023-50387] vulnerability works by using a combination of Keys (also colliding Keys), Signatures and number of RRSETs on a malicious zone. Answers from that zone can force a DNSSEC validator down a very CPU intensive and time costly validation path. The NSEC3 [CVE-2023-50868] vulnerability uses specially crafted responses on a malicious zone with multiple NSEC3 RRSETs to force a DNSSEC validator down a very CPU intensive and time costly NSEC3 hash calculation path. Discovery 2024-02-06 Entry 2024-02-13 Modified 2024-04-01 bind916 < 9.16.48 bind918 < 9.18.24 bind9-devel < 9.19.21 dnsmasq < 2.90 dnsmasq-devel < 2.90 powerdns-recursor < 5.0.2 unbound < 1.19.1 FreeBSD ge 14.0 lt 14.0_6 ge 13.2 lt 13.2_11 CVE-2023-50387 CVE-2023-50868 https://kb.isc.org/docs/cve-2023-50387 https://kb.isc.org/docs/cve-2023-50868 https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html https://blog.powerdns.com/2024/02/13/powerdns-recursor-4-8-6-4-9-3-5-0-2-released https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/ SA-24:03.unbound
75d72e03-b137-11ea-8659-901b0ef719ab	BIND -- Remote Denial of Service vulnerability ISC reports: An assertion check in BIND (that is meant to prevent going beyond the end of a buffer when processing incoming data) can be incorrectly triggered by a large response during zone transfer. Discovery 2020-06-17 Entry 2020-06-18 bind916 ge 9.16.0 lt 9.16.4 CVE-2020-8618 https://kb.isc.org/docs/cve-2020-8618
f00d1873-b138-11ea-8659-901b0ef719ab	BIND -- Remote Denial of Service vulnerability ISC reports: The asterisk character ("*") is allowed in DNS zone files, where it is most commonly present as a wildcard at a terminal node of the Domain Name System graph. However, the RFCs do not require and BIND does not enforce that an asterisk character be present only at a terminal node. A problem can occur when an asterisk is present in an empty non-terminal location within the DNS graph. If such a node exists, after a series of queries, named can reach an inconsistent state that results in the failure of an assertion check in rbtdb.c, followed by the program exiting due to the assertion failure. Discovery 2020-06-17 Entry 2020-06-18 bind911 ge 9.11.14 lt 9.11.20 bind916 ge 9.16.0 lt 9.16.4 CVE-2020-8619 https://kb.isc.org/docs/cve-2020-8619

VuXML ID

Description

21a854cc-cac1-11ee-b7a7-353f1e043d9a

DNSSEC validators -- denial-of-service/CPU exhaustion from KeyTrap and NSEC3 vulnerabilities

Simon Kelley reports:

If DNSSEC validation is enabled, then an attacker who can force a DNS server to validate a specially crafted signed domain can use a lot of CPU in the validator. This only affects dnsmasq installations with DNSSEC enabled.

Stichting NLnet Labs reports:

The KeyTrap [CVE-2023-50387] vulnerability works by using a combination of Keys (also colliding Keys), Signatures and number of RRSETs on a malicious zone. Answers from that zone can force a DNSSEC validator down a very CPU intensive and time costly validation path.

The NSEC3 [CVE-2023-50868] vulnerability uses specially crafted responses on a malicious zone with multiple NSEC3 RRSETs to force a DNSSEC validator down a very CPU intensive and time costly NSEC3 hash calculation path.

Discovery 2024-02-06
Entry 2024-02-13
Modified 2024-04-01
bind916

< 9.16.48

bind918

< 9.18.24

bind9-devel

< 9.19.21

dnsmasq

< 2.90

dnsmasq-devel

< 2.90

powerdns-recursor

< 5.0.2

unbound

< 1.19.1

FreeBSD

ge 14.0 lt 14.0_6

ge 13.2 lt 13.2_11

CVE-2023-50387
CVE-2023-50868
https://kb.isc.org/docs/cve-2023-50387
https://kb.isc.org/docs/cve-2023-50868
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html
https://blog.powerdns.com/2024/02/13/powerdns-recursor-4-8-6-4-9-3-5-0-2-released
https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/
SA-24:03.unbound

75d72e03-b137-11ea-8659-901b0ef719ab

BIND -- Remote Denial of Service vulnerability

ISC reports:

An assertion check in BIND (that is meant to prevent going beyond the end of a buffer when processing incoming data) can be incorrectly triggered by a large response during zone transfer.

Discovery 2020-06-17
Entry 2020-06-18
bind916

ge 9.16.0 lt 9.16.4

CVE-2020-8618
https://kb.isc.org/docs/cve-2020-8618

f00d1873-b138-11ea-8659-901b0ef719ab

BIND -- Remote Denial of Service vulnerability

ISC reports:

The asterisk character ("*") is allowed in DNS zone files, where it is most commonly present as a wildcard at a terminal node of the Domain Name System graph. However, the RFCs do not require and BIND does not enforce that an asterisk character be present only at a terminal node.

A problem can occur when an asterisk is present in an empty non-terminal location within the DNS graph. If such a node exists, after a series of queries, named can reach an inconsistent state that results in the failure of an assertion check in rbtdb.c, followed by the program exiting due to the assertion failure.

Discovery 2020-06-17
Entry 2020-06-18
bind911

ge 9.11.14 lt 9.11.20

bind916

ge 9.16.0 lt 9.16.4

CVE-2020-8619
https://kb.isc.org/docs/cve-2020-8619