Skip to main content
No exploitation reported

CVE-2023-5679

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 bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled. This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.12-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 18:48 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-5679?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-5679?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Isc bind
BranchAffectedFixed in
9.16≥ 9.16.12, ≤ 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.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
9.16= 9.16.45no fix published
9.18= 9.18.11no fix published
Fedoraproject fedora
BranchAffectedFixed in
38.x= 38no fix published
39.x= 39no fix published
Netapp active iq unified manager
BranchAffectedFixed in
—all versionsno fix published

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

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

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-5679?

A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive resolution, when both of these features are enabled. This issue affects BIND 9 versions 9.16.12 through 9.16.45, 9.18.0 through 9.18.21, 9.19.0 through 9.19.19, 9.16.12-S1 through 9.16.45-S1, and 9.18.11-S1 through 9.18.21-S1.

Is CVE-2023-5679 actively exploited?

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

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

CVE-2023-5679 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.

Hear about the next vulnerability in your software

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