There are 13 open security issues in buster.
12 important issues:
- CVE-2019-25031:
Unbound before 1.9.5 allows configuration injection in create_unbound_ad_servers.sh upon a successful man-in-the-middle attack against a cleartext HTTP session.
- CVE-2019-25032:
Unbound before 1.9.5 allows an integer overflow in the regional allocator via regional_alloc.
- CVE-2019-25033:
Unbound before 1.9.5 allows an integer overflow in the regional allocator via the ALIGN_UP macro.
- CVE-2019-25034:
Unbound before 1.9.5 allows an integer overflow in sldns_str2wire_dname_buf_origin, leading to an out-of-bounds write.
- CVE-2019-25035:
Unbound before 1.9.5 allows an out-of-bounds write in sldns_bget_token_par.
- CVE-2019-25036:
Unbound before 1.9.5 allows an assertion failure and denial of service in synth_cname.
- CVE-2019-25037:
Unbound before 1.9.5 allows an assertion failure and denial of service in dname_pkt_copy via an invalid packet.
- CVE-2019-25038:
Unbound before 1.9.5 allows an integer overflow in a size calculation in dnscrypt/dnscrypt.c.
- CVE-2019-25039:
Unbound before 1.9.5 allows an integer overflow in a size calculation in respip/respip.c.
- CVE-2019-25040:
Unbound before 1.9.5 allows an infinite loop via a compressed name in dname_pkt_copy.
- CVE-2019-25041:
Unbound before 1.9.5 allows an assertion failure via a compressed name in dname_pkt_copy.
- CVE-2019-25042:
Unbound before 1.9.5 allows an out-of-bounds write via a compressed name in rdata_copy.
1 issue left for the package maintainer to handle:
- CVE-2020-28935:
(needs triaging)
NLnet Labs Unbound, up to and including version 1.12.0, and NLnet Labs NSD, up to and including version 4.3.3, contain a local vulnerability that would allow for a local symlink attack. When writing the PID file, Unbound and NSD create the file if it is not there, or open an existing file for writing. In case the file was already present, they would follow symlinks if the file happened to be a symlink instead of a regular file. An additional chown of the file would then take place after it was written, making the user Unbound/NSD is supposed to run as the new owner of the file. If an attacker has local access to the user Unbound/NSD runs as, she could create a symlink in place of the PID file pointing to a file that she would like to erase. If then Unbound/NSD is killed and the PID file is not cleared, upon restarting with root privileges, Unbound/NSD will rewrite any file pointed at by the symlink. This is a local vulnerability that could create a Denial of Service of the system Unbound/NSD is running on. It requires an attacker having access to the limited permission user Unbound/NSD runs as and point through the symlink to a critical file on the system.
You can find information about how to handle this issue in the security team's documentation.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/u/unbound.png){kind=link}