PT-2020-6803 · Nlnet+8 · Nsd+9
Mason Loring Bliss
·
Published
2020-09-09
·
Updated
2025-05-08
·
CVE-2020-28935
CVSS v3.1
5.5
Medium
| Vector | AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Name of the Vulnerable Software and Affected Versions
NLnet Labs Unbound versions up to and including 1.12.0
NLnet Labs NSD versions up to and including 4.3.3
Description
The issue is related to a local vulnerability that allows 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. If 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. This is a local vulnerability that could create a Denial of Service of the system Unbound/NSD is running on.
Recommendations
For NLnet Labs Unbound versions up to and including 1.12.0, consider disabling the PID file writing functionality until a patch is available.
For NLnet Labs NSD versions up to and including 4.3.3, restrict access to the PID file to minimize the risk of exploitation.
As a temporary workaround, consider removing the symlink functionality for the PID file until a patch is available.
At the moment, there is no information about a newer version that contains a fix for this vulnerability.
DoS
Link Following
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Alt Linux
Astra Linux
Centos
Linuxmint
Nsd
Red Hat
Rocky Linux
Suse
Ubuntu
Unbound