openwrtv3/package/network/services/dnsmasq/patches
Kevin Darbyshire-Bryant a3198061f8 dnsmasq: backport dnssec security fix
CVE-2017-15107

An interesting problem has turned up in DNSSEC validation. It turns out
that NSEC records expanded from wildcards are allowed, so a domain can
include an NSEC record for *.example.org and an actual query reply could
expand that to anything in example.org  and still have it signed by the
signature for the wildcard. So, for example

!.example.org NSEC zz.example.org

is fine.

The problem is that most implementers (your author included, but also
the Google public DNS people, powerdns and Unbound) then took that
record to prove the nothing exists between !.example.org and
zz.example.org, whereas in fact it only provides that proof between
*.example.org and zz.example.org.

This gives an attacker a way to prove that anything between
!.example.org and *.example.org doesn't exists, when it may well do so.

Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
2018-01-19 22:11:16 +01:00
..
110-ipset-remove-old-kernel-support.patch dnsmasq: update to dnsmasq 2.77test1 2017-02-05 22:26:23 +01:00
210-dnssec-improve-timestamp-heuristic.patch dnsmasq: bump to 2.77rc3 2017-05-12 21:30:56 +02:00
230-fix-poll-h-include-warning-on-musl.patch dnsmasq: bump to v2.78 2017-10-02 18:26:53 +02:00
240-ubus.patch dnsmasq: backport infinite dns retries fix 2017-12-06 14:55:12 +01:00
250-Fix-infinite-retries-in-strict-order-mode.patch dnsmasq: backport infinite dns retries fix 2017-12-06 14:55:12 +01:00
260-dnssec-SIGINT.patch dnsmasq: use SIGINT for dnssec time valid 2018-01-15 22:34:51 +01:00
270-dnssec-wildcards.patch dnsmasq: backport dnssec security fix 2018-01-19 22:11:16 +01:00