Skip to content
Fencer Intel
high 7.8

CVE-2013-2266 in the critical feed json

libdns in ISC BIND 9.7.x and 9.8.x before 9.8.4-P2, 9.8.5 before 9.8.5b2, 9.9.x before 9.9.2-P2, and 9.9.3 before 9.9.3b2 on UNIX platforms…

published 13y ago modified 4mo ago also EUVD-2013-2212

cvss
7.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
42.9%
EPSS 42.9% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

libdns in ISC BIND 9.7.x and 9.8.x before 9.8.4-P2, 9.8.5 before 9.8.5b2, 9.9.x before 9.9.2-P2, and 9.9.3 before 9.9.3b2 on UNIX platforms allows remote attackers to cause a denial of service (memory consumption) via a crafted regular expression, as demonstrated by a memory-exhaustion attack against a machine running a named process.

Patch / fix

  • bind9 Debian 14, Debian 13, Debian 12 1:9.8.4.dfsg.P1-6+nmu1

debian advisories DEBIAN-CVE-2013-2266

  • bind97 RHEL 5 32:9.7.0-17.P2.el5_9.1
  • bind97-libs RHEL 5 32:9.7.0-17.P2.el5_9.1
  • bind97-utils RHEL 5 32:9.7.0-17.P2.el5_9.1
  • bind97-chroot RHEL 5 32:9.7.0-17.P2.el5_9.1
  • bind RHEL 6 32:9.8.2-0.17.rc1.el6_4.4
  • bind-sdb RHEL 6 32:9.8.2-0.17.rc1.el6_4.4
  • bind-libs RHEL 6 32:9.8.2-0.17.rc1.el6_4.4
  • bind-utils RHEL 6 32:9.8.2-0.17.rc1.el6_4.4

red hat advisories RHSA-2013:0690RHSA-2013:0689

  • dhcp openSUSE Tumbleweed 4.3.3.P1-3.1
  • bind openSUSE Tumbleweed 9.10.3P4-21.1

opensuse advisories openSUSE-SU-2024:10358-1openSUSE-SU-2024:10467-1

Is CVE-2013-2266 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-2266 updated cvss 5.0

bind: libdns regular expressions excessive resource consumption DoS

  • Red Hat Enterprise Linux (v. 5 server) bind97 9.7.0-17.P2.el5_9.1, bind97-libs 9.7.0-17.P2.el5_9.1, bind97-utils 9.7.0-17.P2.el5_9.1, bind97-chroot 9.7.0-17.P2.el5_9.1
    fixed: vendor fix RHSA-2013:0690
  • Red Hat Enterprise Linux Desktop (v. 6) bind 9.8.2-0.17.rc1.el6_4.4, bind-libs 9.8.2-0.17.rc1.el6_4.4, bind-utils 9.8.2-0.17.rc1.el6_4.4 Red Hat Enterprise Linux Desktop Optional (v. 6) bind 9.8.2-0.17.rc1.el6_4.4, bind-sdb 9.8.2-0.17.rc1.el6_4.4, bind-chroot 9.8.2-0.17.rc1.el6_4.4 Red Hat Enterprise Linux HPC Node (v. 6) bind 9.8.2-0.17.rc1.el6_4.4, bind-libs 9.8.2-0.17.rc1.el6_4.4, bind-utils 9.8.2-0.17.rc1.el6_4.4 Red Hat Enterprise Linux HPC Node Optional (v. 6) bind 9.8.2-0.17.rc1.el6_4.4, bind-sdb 9.8.2-0.17.rc1.el6_4.4, bind-chroot 9.8.2-0.17.rc1.el6_4.4 Red Hat Enterprise Linux Server (v. 6) bind 9.8.2-0.17.rc1.el6_4.4, bind-libs 9.8.2-0.17.rc1.el6_4.4, bind-utils 9.8.2-0.17.rc1.el6_4.4, bind-chroot 9.8.2-0.17.rc1.el6_4.4 Red Hat Enterprise Linux Server Optional (v. 6) bind 9.8.2-0.17.rc1.el6_4.4, bind-sdb 9.8.2-0.17.rc1.el6_4.4
    +2 more products
    Red Hat Enterprise Linux Workstation (v. 6) bind 9.8.2-0.17.rc1.el6_4.4, bind-libs 9.8.2-0.17.rc1.el6_4.4, bind-utils 9.8.2-0.17.rc1.el6_4.4, bind-chroot 9.8.2-0.17.rc1.el6_4.4 Red Hat Enterprise Linux Workstation Optional (v. 6) bind 9.8.2-0.17.rc1.el6_4.4, bind-sdb 9.8.2-0.17.rc1.el6_4.4
    fixed: vendor fix RHSA-2013:0689
  • Red Hat Enterprise Linux 4 bind Red Hat Enterprise Linux 5 bind
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

42.85% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 7.8 AV:N/AC:L/Au:N/C:N/I:N/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.