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.
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Name_server_daemon | Nlnetlabs | * | 4.3.4 (excluding) |
| Unbound | Nlnetlabs | * | 1.13.0 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | unbound-0:1.7.3-15.el8 | * |
| Red Hat Enterprise Linux 8.2 Extended Update Support | RedHat | unbound-0:1.7.3-12.el8_2 | * |
| Unbound | Ubuntu | bionic | * |
| Unbound | Ubuntu | esm-infra-legacy/trusty | * |
| Unbound | Ubuntu | esm-infra/xenial | * |
| Unbound | Ubuntu | focal | * |
| Unbound | Ubuntu | groovy | * |
| Unbound | Ubuntu | trusty | * |
| Unbound | Ubuntu | trusty/esm | * |
| Unbound | Ubuntu | xenial | * |