fkie_cve-2025-40777
Vulnerability from fkie_nvd
Published
2025-07-16 18:15
Modified
2025-11-04 22:16
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
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.
References
security-officer@isc.orghttps://kb.isc.org/docs/cve-2025-40777
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2025/07/16/6
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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.\nThis 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."
    },
    {
      "lang": "es",
      "value": "Si un solucionador de cach\u00e9 con nombre est\u00e1 configurado con `serve-stale-enable` `yes` y con `stale-answer-client-timeout` establecido en `0` (el \u00fanico valor permitido aparte de `disabled`), y si el solucionador, al resolver una consulta, encuentra una cadena CNAME que involucra una combinaci\u00f3n espec\u00edfica de registros en cach\u00e9 o autorizados, el daemon se interrumpir\u00e1 con un error de aserci\u00f3n. Este problema afecta a las versiones de BIND 9 de la 9.20.0 a la 9.20.10, de la 9.21.0 a la 9.21.9 y de la 9.20.9-S1 a la 9.20.10-S1."
    }
  ],
  "id": "CVE-2025-40777",
  "lastModified": "2025-11-04T22:16:11.553",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6,
        "source": "security-officer@isc.org",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-07-16T18:15:24.770",
  "references": [
    {
      "source": "security-officer@isc.org",
      "url": "https://kb.isc.org/docs/cve-2025-40777"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "http://www.openwall.com/lists/oss-security/2025/07/16/6"
    }
  ],
  "sourceIdentifier": "security-officer@isc.org",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-617"
        }
      ],
      "source": "security-officer@isc.org",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.