If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-client-timeout` set to `0` (the only allowable value other than `disabled`), and if the resolver, in the process of resolving a query, encounters a CNAME chain involving a specific combination of cached or authoritative records, the daemon will abort with an assertion failure. This issue affects BIND 9 versions 9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1.

The version of ISC BIND installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the cve-2025-40777 advisory.

  - If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-     client-timeout` set to `0` (the only allowable value other than `disabled`), and if the resolver, in the     process of resolving a query, encounters a CNAME chain involving a specific combination of cached or     authoritative records, the daemon will abort with an assertion failure. This issue affects BIND 9 versions     9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1. (CVE-2025-40777)

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

An update of the bindutils package has been released.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-     client-timeout` set to `0` (the only allowable value other than `disabled`), and if the resolver, in the     process of resolving a query, encounters a CNAME chain involving a specific combination of cached or     authoritative records, the daemon will abort with an assertion failure. This issue affects BIND 9 versions     9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1. (CVE-2025-40777)

Note that Nessus relies on the presence of the package as reported by the vendor.

It is, therefore, affected by a vulnerability as referenced in the ALAS2023-2025-1105 advisory.

    If a `named` caching resolver is configured with `serve-stale-enable` `yes`, and with `stale-answer-     client-timeout` set to `0` (the only allowable value other than `disabled`), and if the resolver, in the     process of resolving a query, encounters a CNAME chain involving a specific combination of cached or     authoritative records, the daemon will abort with an assertion failure.This issue affects BIND 9 versions     9.20.0 through 9.20.10, 9.21.0 through 9.21.9, and 9.20.9-S1 through 9.20.10-S1. (CVE-2025-40777)

Tenable has extracted the preceding description block directly from the tested product security advisory.

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

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2025:02349-1 advisory.

    - Upgrade to release 9.20.11
    - CVE-2025-40777: Fixed a possible assertion failure when stale-answer-client-timeout is set to 0.
    (bsc#1246548)

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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

The remote Ubuntu 25.04 host has packages installed that are affected by a vulnerability as referenced in the USN-7641-1 advisory.

    It was discovered that Bind incorrectly handled configurations where the stale-answer-client-timeout     option is set to 0. A remote attacker could possibly use this issue to cause Bind to crash, resulting in a     denial of service.

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

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

The version of bind installed on the remote host is prior to 9.18.38 / 9.20.11. It is, therefore, affected by a vulnerability as referenced in the SSA:2025-197-01 advisory.

    New bind packages are available for Slackware 15.0 and -current to fix a security issue.

Tenable has extracted the preceding description block directly from the bind security advisory.

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

ID	Name	Product	Family	Severity
298820	ISC BIND 9.20.0 < 9.20.11 / 9.20.9-S1 < 9.20.11-S1 / 9.21.0 < 9.21.10 Assertion Failure (cve-2025-40777)	Nessus	DNS	high
253439	Photon OS 5.0: Bindutils PHSA-2025-5.0-0595	Nessus	PhotonOS Local Security Checks	high
246214	Linux Distros Unpatched Vulnerability : CVE-2025-40777	Nessus	Misc.	high
243485	Amazon Linux 2023 : bind, bind-chroot, bind-devel (ALAS2023-2025-1105)	Nessus	Amazon Linux Local Security Checks	high
242301	SUSE SLED15 / SLES15 Security Update : bind (SUSE-SU-2025:02349-1)	Nessus	SuSE Local Security Checks	high
242281	Ubuntu 25.04 : Bind vulnerability (USN-7641-1)	Nessus	Ubuntu Local Security Checks	high
242196	Slackware Linux 15.0 / current bind Vulnerability (SSA:2025-197-01)	Nessus	Slackware Local Security Checks	high

Detections

Analytics

CVE-2025-40777

high

Tenable Plugins

high

high

high

high

high

high

high