Skip to main content
No exploitation reportedFix available

CVE-2023-3341

No exploitation reported by the sources we read.

  • Published2023-09-20
  • Fixed in9.19.17 · 9.18.19 · 9.16.44
  • WeaknessCWE-1325 · CWE-787

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

The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of available stack memory, causing `named` to terminate unexpectedly. Since each incoming control channel message is fully parsed before its contents are authenticated, exploiting this flaw does not require the attacker to hold a valid RNDC key; only network access to the control channel's configured TCP port is necessary. This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1.

Timeline

dates in UTC
  1. 2023-09-2013: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-3341?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-3341?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.19≥ 9.19.0, < 9.19.179.19.17
9.18≥ 9.18.0, < 9.18.199.18.19
9.x≥ 9.2.0, < 9.16.449.16.44
9.9= 9.9.3no fix published
9.9= 9.9.12no fix published
9.9= 9.9.13no fix published
9.10= 9.10.5no fix published
9.10= 9.10.7no fix published
9.11= 9.11.3no fix published
9.11= 9.11.4no fix published
9.11= 9.11.5no fix published
9.11= 9.11.6no fix published
Debian debian linux
BranchAffectedFixed in
10.0= 10.0no fix published
11.0= 11.0no fix published
Fedoraproject fedora
BranchAffectedFixed in
37.x= 37no fix published
38.x= 38no fix published

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-11.el9_2.2and 9 other packages
  • bindAlmaLinux:8all versions · fixed in 32:9.11.36-8.el8_8.2and 16 other packages
  • bind9.16AlmaLinux:8all versions · fixed in 32:9.16.23-0.14.el8_8.2.alma.1and 8 other packages

Full record on NVD

Fix

  1. Update Isc bind to 9.19.17 · 9.18.19 · 9.16.44

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 decisionnone2025-06-03
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.17.5read 2026-10-23
  • CISA-ADPweakness (CWE)CWE-13252025-06-03
  • NVDweakness (CWE)CWE-787read 2026-10-23
  • FIRST EPSSEPSS score3.0 %2026-10-23
  • 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
2023-09-20
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2023-3341?

The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of available stack memory, causing `named` to terminate unexpectedly. Since each incoming control channel message is fully parsed before its contents are authenticated, exploiting this flaw does not require the attacker to hold a valid RNDC key; only network access to the control channel's configured TCP port is necessary. This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1.

Is CVE-2023-3341 actively exploited?

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

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

CVE-2023-3341 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 ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

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

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database