Skip to content
Fencer Intel
low 2.6

CVE-2010-0213 json

BIND 9.7.1 and 9.7.1-P1, when a recursive validating server has a trust anchor that is configured statically or via DNSSEC Lookaside Valida…

published 16y ago modified 4mo ago also EUVD-2010-0244

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

Summary

BIND 9.7.1 and 9.7.1-P1, when a recursive validating server has a trust anchor that is configured statically or via DNSSEC Lookaside Validation (DLV), allows remote attackers to cause a denial of service (infinite loop) via a query for an RRSIG record whose answer is not in the cache, which causes BIND to repeatedly send RRSIG queries to the authoritative servers.

Patch / fix

  • bind9 Debian 14, Debian 13, Debian 12 9.7.1.dfsg.P2

debian advisories DEBIAN-CVE-2010-0213

Is CVE-2010-0213 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-2010-0213 updated cvss 4.3

BIND: DoS (infinite loop of RRSIGs queries to authoritative servers) via certain RRSIG query

  • Red Hat Enterprise Linux 4 bind Red Hat Enterprise Linux 5 bind Red Hat Enterprise Linux 6 bind, bind-sdb, bind-libs, bind-utils, bind-chroot
    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

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

CVSS scores

assigned by version score vector
NVD 2.0 2.6 AV:N/AC:H/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-19 Data Processing Errors

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.