Several security vulnerabilities have been discovered in Unbound, a validating, recursive, caching DNS resolver, by security researchers of X41 D-SEC located in Aachen, Germany. Integer overflows, assertion failures, an out-of-bound write and an infinite loop vulnerability may lead to a denial of service or have a negative impact on data confidentiality.

For Debian 9 stretch, these problems have been fixed in version 1.9.0-2+deb10u2~deb9u2.

We recommend that you upgrade your unbound1.9 packages.

For the detailed security status of unbound1.9 please refer to its security tracker page at:
https://security-tracker.debian.org/tracker/unbound1.9

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote SUSE Linux SLED15 / SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:0176-1 advisory.

  - ** DISPUTED ** 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. NOTE: The vendor does not consider     this a vulnerability of the Unbound software. create_unbound_ad_servers.sh is a contributed script from     the community that facilitates automatic configuration creation. It is not part of the Unbound     installation. (CVE-2019-25031)

  - ** DISPUTED ** Unbound before 1.9.5 allows an integer overflow in the regional allocator via     regional_alloc. NOTE: The vendor disputes that this is a vulnerability. Although the code may be     vulnerable, a running Unbound installation cannot be remotely or locally exploited. (CVE-2019-25032)

  - ** DISPUTED ** Unbound before 1.9.5 allows an integer overflow in the regional allocator via the ALIGN_UP     macro. NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a     running Unbound installation cannot be remotely or locally exploited. (CVE-2019-25033)

  - ** DISPUTED ** Unbound before 1.9.5 allows an integer overflow in sldns_str2wire_dname_buf_origin, leading     to an out-of-bounds write. NOTE: The vendor disputes that this is a vulnerability. Although the code may     be vulnerable, a running Unbound installation cannot be remotely or locally exploited. (CVE-2019-25034)

  - ** DISPUTED ** Unbound before 1.9.5 allows an out-of-bounds write in sldns_bget_token_par. NOTE: The     vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running Unbound     installation cannot be remotely or locally exploited. (CVE-2019-25035)

  - ** DISPUTED ** Unbound before 1.9.5 allows an assertion failure and denial of service in synth_cname.
    NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running     Unbound installation cannot be remotely or locally exploited. (CVE-2019-25036)

  - ** DISPUTED ** Unbound before 1.9.5 allows an assertion failure and denial of service in dname_pkt_copy     via an invalid packet. NOTE: The vendor disputes that this is a vulnerability. Although the code may be     vulnerable, a running Unbound installation cannot be remotely or locally exploited. (CVE-2019-25037)

  - ** DISPUTED ** Unbound before 1.9.5 allows an integer overflow in a size calculation in     dnscrypt/dnscrypt.c. NOTE: The vendor disputes that this is a vulnerability. Although the code may be     vulnerable, a running Unbound installation cannot be remotely or locally exploited. (CVE-2019-25038)

  - ** DISPUTED ** Unbound before 1.9.5 allows an integer overflow in a size calculation in respip/respip.c.
    NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running     Unbound installation cannot be remotely or locally exploited. (CVE-2019-25039)

  - ** DISPUTED ** Unbound before 1.9.5 allows an infinite loop via a compressed name in dname_pkt_copy. NOTE:
    The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running Unbound     installation cannot be remotely or locally exploited. (CVE-2019-25040)

  - ** DISPUTED ** Unbound before 1.9.5 allows an assertion failure via a compressed name in dname_pkt_copy.
    NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running     Unbound installation cannot be remotely or locally exploited. (CVE-2019-25041)

  - ** DISPUTED ** Unbound before 1.9.5 allows an out-of-bounds write via a compressed name in rdata_copy.
    NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running     Unbound installation cannot be remotely or locally exploited. (CVE-2019-25042)

  - 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. (CVE-2020-28935)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:0176-2 advisory.

  - ** DISPUTED ** 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. NOTE: The vendor does not consider     this a vulnerability of the Unbound software. create_unbound_ad_servers.sh is a contributed script from     the community that facilitates automatic configuration creation. It is not part of the Unbound     installation. (CVE-2019-25031)

  - ** DISPUTED ** Unbound before 1.9.5 allows an integer overflow in the regional allocator via     regional_alloc. NOTE: The vendor disputes that this is a vulnerability. Although the code may be     vulnerable, a running Unbound installation cannot be remotely or locally exploited. (CVE-2019-25032)

  - ** DISPUTED ** Unbound before 1.9.5 allows an integer overflow in the regional allocator via the ALIGN_UP     macro. NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a     running Unbound installation cannot be remotely or locally exploited. (CVE-2019-25033)

  - ** DISPUTED ** Unbound before 1.9.5 allows an integer overflow in sldns_str2wire_dname_buf_origin, leading     to an out-of-bounds write. NOTE: The vendor disputes that this is a vulnerability. Although the code may     be vulnerable, a running Unbound installation cannot be remotely or locally exploited. (CVE-2019-25034)

  - ** DISPUTED ** Unbound before 1.9.5 allows an out-of-bounds write in sldns_bget_token_par. NOTE: The     vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running Unbound     installation cannot be remotely or locally exploited. (CVE-2019-25035)

  - ** DISPUTED ** Unbound before 1.9.5 allows an assertion failure and denial of service in synth_cname.
    NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running     Unbound installation cannot be remotely or locally exploited. (CVE-2019-25036)

  - ** DISPUTED ** Unbound before 1.9.5 allows an assertion failure and denial of service in dname_pkt_copy     via an invalid packet. NOTE: The vendor disputes that this is a vulnerability. Although the code may be     vulnerable, a running Unbound installation cannot be remotely or locally exploited. (CVE-2019-25037)

  - ** DISPUTED ** Unbound before 1.9.5 allows an integer overflow in a size calculation in     dnscrypt/dnscrypt.c. NOTE: The vendor disputes that this is a vulnerability. Although the code may be     vulnerable, a running Unbound installation cannot be remotely or locally exploited. (CVE-2019-25038)

  - ** DISPUTED ** Unbound before 1.9.5 allows an integer overflow in a size calculation in respip/respip.c.
    NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running     Unbound installation cannot be remotely or locally exploited. (CVE-2019-25039)

  - ** DISPUTED ** Unbound before 1.9.5 allows an infinite loop via a compressed name in dname_pkt_copy. NOTE:
    The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running Unbound     installation cannot be remotely or locally exploited. (CVE-2019-25040)

  - ** DISPUTED ** Unbound before 1.9.5 allows an assertion failure via a compressed name in dname_pkt_copy.
    NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running     Unbound installation cannot be remotely or locally exploited. (CVE-2019-25041)

  - ** DISPUTED ** Unbound before 1.9.5 allows an out-of-bounds write via a compressed name in rdata_copy.
    NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running     Unbound installation cannot be remotely or locally exploited. (CVE-2019-25042)

  - 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. (CVE-2020-28935)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
149342	Debian DLA-2652-1 : unbound1.9 security update	Nessus	Debian Local Security Checks	5/7/2021	1/12/2024	critical
157078	SUSE SLED15 / SLES15 Security Update : unbound (SUSE-SU-2022:0176-1)	Nessus	SuSE Local Security Checks	1/26/2022	7/14/2023	critical
158091	SUSE SLES15 Security Update : unbound (SUSE-SU-2022:0176-2)	Nessus	SuSE Local Security Checks	2/16/2022	7/13/2023	critical

Detections

Analytics

Plugins Search

critical

critical

critical