Breaking: Cry2Wolf - Not Every Branded Bug Deserves a Fire Drill
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2010-3613

bind: failure to clear existing RRSIG records when a NO DATA is negatively cached could DoS named

Overview

Published
6 Dec 2010
Modified
29 Apr 2026
Medium CVE
0 Registry packages
33 OS packages
4 Linux distributions
Yes Fix available

Description

named in ISC BIND 9.6.2 before 9.6.2-P3, 9.6-ESV before 9.6-ESV-R3, and 9.7.x before 9.7.2-P3 does not properly handle the combination of signed negative responses and corresponding RRSIG records in the cache, which allows remote attackers to cause a denial of service (daemon crash) via a query for cached data.

Source: OX vulnerability database

Severity

4 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:S/C:N/I:N/A:P

Weakness: CWE-264

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

debian 4 releases · 1 package

fixed 4
bind9
debian fixes for CVE-2010-3613
ReleasePackageFixed in
11 bind9 1:9.7.2.dfsg.P3-1
12 bind9 1:9.7.2.dfsg.P3-1
13 bind9 1:9.7.2.dfsg.P3-1
14 bind9 1:9.7.2.dfsg.P3-1

echo 1 release · 1 package

fixed 1
bind9
echo fixes for CVE-2010-3613
ReleasePackageFixed in
bind9 1:9.7.2.dfsg.P3-1

openSUSE 1 release · 2 packages

fixed 2
idnkit bind
openSUSE fixes for CVE-2010-3613
ReleasePackageFixed inAdvisory
Tumbleweed idnkit +8 1.0-21.1 openSUSE-SU-2024:10467-1
Tumbleweed bind +21 9.10.3P4-21.1 openSUSE-SU-2024:10467-1

root.io debian 1 release · 1 package

fixed 1
rootio-bind9
root.io debian fixes for CVE-2010-3613
ReleasePackageFixed in
11 rootio-bind9 1:9.7.2.dfsg.P3-1

References

Show all 42 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.