Skip to content
WatchlistCritical

CVE-2001-0010Bind Vulnerability

Buffer overflow in transaction signature (TSIG) handling code in BIND 8 allows remote attackers to gain root privileges.

Published Jan 29, 2001 · Updated Aug 8, 2024

Key Facts

Patch immediately
  • CVE-2001-0010 is a critical-severity vulnerability (CVSS 10.0 v2) affecting Bind (Isc).
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 32% probability of exploitation in the next 30 days.
  • No fixed version is listed yet; check the vendor advisory for mitigations.
  • Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Scores

CVSS v2

10.0

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

EPSS (30-day exploit likelihood)

32%

Higher than 98.2% of all scored CVEs

Exploit maturity

Proof of concept

ATLAS score

49/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

4

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Advisories And Exploit References

Description

Buffer overflow in transaction signature (TSIG) handling code in BIND 8 allows remote attackers to gain root privileges.

Affected Products

10 affected entries in total
ProductAffected versionsFixed in
BindIsc8.2, 8.2.1, 8.2.2, 8.2.2-p1, 8.2.2-p2, 8.2.2-p3, 8.2.2-p4, 8.2.2-p5n/a

Timeline

  1. Publicly disclosed

    Jan 29, 2001

  2. Last updated

    Aug 8, 2024

References

5 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2001-0010 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.