Skip to main content
No exploitation reported

CVE-2023-5517

No exploitation reported by the sources we read.

  • Published2024-02-13
  • WeaknessCWE-617

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2024-02-1314:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-5517?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-5517?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · CISA-ADP
Isc bind
BranchAffectedFixed in
9.x≥ 9.12.0, ≤ 9.16.45no fix published
9.18≥ 9.18.0, ≤ 9.18.21no fix published
9.19≥ 9.19.0, ≤ 9.19.19no fix published
9.16= 9.16.8no fix published
9.16= 9.16.11no fix published
9.16= 9.16.12no fix published
9.16= 9.16.13no fix published
9.16= 9.16.14no fix published
9.16= 9.16.21no fix published
9.16= 9.16.32no fix published
9.16= 9.16.36no fix published
9.16= 9.16.43no fix published
Isc bind 9
BranchAffectedFixed in
9.x≥ 9.12.0, ≤ 9.16.45no fix published
9.18≥ 9.18.0, ≤ 9.18.21no fix published
9.19≥ 9.19.0, ≤ 9.19.19no fix published
9.16≥ 9.16.8-S1, ≤ 9.16.45-S1no fix published
9.18≥ 9.18.11-S1, ≤ 9.18.21-S1no fix published
Fedoraproject fedora
BranchAffectedFixed in
38.x= 38no fix published
39.x= 39no fix published

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • bindAlmaLinux:9all versions · fixed in 32:9.16.23-14.el9_3.4and 9 other packages
  • bindAlmaLinux:9all versions · fixed in 32:9.16.23-18.el9_4.1and 9 other packages
  • bind-dyndb-ldapAlmaLinux:9all versions · fixed in 11.9-8.el9_3.3.alma.1
  • bind-dyndb-ldapAlmaLinux:9all versions · fixed in 11.9-9.el9_4.alma.1
  • bind9.16AlmaLinux:8all versions · fixed in 32:9.16.23-0.16.el8_9.2.alma.1and 8 other packages

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2024-08-22
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.17.5read 2026-10-23
  • CISA-ADPweakness (CWE)CWE-6172024-08-22
  • NVDweakness (CWE)CWE-617read 2026-10-23
  • FIRST EPSSEPSS score1.3 %2026-10-22
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2024-02-13
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2023-5517?

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.

Is CVE-2023-5517 actively exploited?

Active exploitation of CVE-2023-5517 has not been confirmed. Its EPSS score was 1.3% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-5517?

CVE-2023-5517 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running bind? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month