CVE-2023-5517
Reported by isc · Published February 13, 2024
A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when: - `nxdomain-redirect <domain>;` is configured, and - the resolver receives a PTR query for an RFC 1918 address that would normally result in an authoritative NXDOMAIN response. This issue affects BIND 9 versions 9.12.0 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.8-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| bind-pkcs11-utils | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| bind-dnssec-utils | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| bind | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| bind-pkcs11 | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| bind-doc | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| bind-utils | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| bind-dlz-filesystem | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| bind-pkcs11-devel | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| bind-pkcs11-libs | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| bind-dlz-sqlite3 | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| bind-devel | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
| python3-bind | Amazon Linux | 32:9.16.48-1.amzn2023.0.1 |
12 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| ISC | BIND 9 | 9.12.0, 9.18.0, 9.19.0 |
| amazon:2023 | bind-pkcs11-utils | 0 |
| amazon:2023 | bind-dnssec-utils | 0 |
| amazon:2023 | bind | 0 |
| amazon:2023 | bind-pkcs11 | 0 |
| amazon:2023 | bind-doc | 0 |
| amazon:2023 | bind-utils | 0 |
| amazon:2023 | bind-dlz-filesystem | 0 |
| amazon:2023 | bind-pkcs11-devel | 0 |
| amazon:2023 | bind-pkcs11-libs | 0 |
| amazon:2023 | bind-dlz-sqlite3 | 0 |
| amazon:2023 | bind-devel | 0 |
| amazon:2023 | python3-bind | 0 |
| amazon:2023 | bind-dlz-mysql | 0 |
| alpine | bind | 0, 0 |
| amazon:2023 | bind-dnssec-doc | 0 |
| isc | bind_9 | 9.18.0, 9.18.11-S1, 9.16.8-S1 |
| wolfi | bind | 0 |
| amazon:2023 | bind-libs | 0 |
| amazon:2023 | bind-license | 0 |
…and 4 more
Timeline
- Feb 13, 2024 CVE Published
- Feb 14, 2024 EPSS Score (30 in total, the first dated here)
- Oct 5, 2024 Coalition ESS Score (9 in total, the first dated here)
- Nov 21, 2024 CVE Updated
- Jun 2, 2026 Security Advisory (51 in total, the first dated here)
- Nov 1, 2026 Distribution Patch (48 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2023-5517
vulnetix vdb fixes CVE-2023-5517Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2023-5517/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- CVE-2023-5517 vendor-advisory