CVE Tools
Track your stack

CVE-2023-5679

Enabling both DNS64 and serve-stale may cause an assertion failure during recursive resolution

No known exploitation. EPSS puts it in the 70th percentile. A vendor fix is available.

CVSS 3.17.5HighEPSS percentile70th1.3% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFixVendor fixNo build named by the sources
Check it yourself

OpenVAS · 47 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.114426

Run the check

Published Updated Sources: CVE.org, NVD, BDU, CSAF

NVD CVE.org

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • ISC BIND 9Affected: ≥ 9.16.12, ≤ 9.16.45Upgrade to: after 9.16.45Affected: ≥ 9.18.0, ≤ 9.18.21Upgrade to: after 9.18.21Affected: ≥ 9.19.0, ≤ 9.19.19Upgrade to: after 9.19.19Affected: ≥ 9.16.12-S1, ≤ 9.16.45-S1Upgrade to: after 9.16.45-S1 + 1 more branchStated by: CVE record
  • Isc BindAffected: ≥ 9.16.12, ≤ 9.16.45Upgrade to: after 9.16.45Stated by: NVD
  • Novell Inc. OpenSUSE LeapAffected: 15.5Upgrade to: not statedStated by: BDU
  • Red Hat Inc. Red Hat Enterprise LinuxAffected: 8Upgrade to: not statedStated by: BDU
  • Сообщество свободного программного обеспечения Debian GNU/LinuxAffected: 10Upgrade to: not statedStated by: BDU

Versions as the sources state them. 15 more products have version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS70th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.3% chance of exploitation activity in the next 30 days, which ranks it in the 70th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 863 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availableworkaround available, record updated
  3. Publishedweakness classified, att&ck mapped

Affected products

And 11 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 28 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for OpenSUSE Leap, not every advisory.