CVE-2000-0335: High severity GNU glibc vulnerability
The resolver in glibc 2.1.3 uses predictable IDs, which allows a local attacker to spoof DNS query results.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Reduce exposure to local attackers by restricting untrusted local user access to affected hosts (host-based access controls, stricter local account policies, or isolating affected systems on the network) until vendor patches are applied.
- Operational
Inventory systems to identify installations of glibc 2.1.3 and ISC BIND 9. Prioritize systems running glibc 2.1.3 (resolver uses predictable IDs) for remediation and apply vendor-supplied patches or updates when they become available.
Event History
Frequently Asked Questions
What is the severity of CVE-2000-0335?
CVE-2000-0335 is classified as a high-severity vulnerability due to its potential for DNS spoofing attacks.
How do I fix CVE-2000-0335?
To mitigate CVE-2000-0335, upgrade the glibc to a version later than 2.1.3 and ensure that BIND is updated to a secure version.
What systems are affected by CVE-2000-0335?
CVE-2000-0335 affects systems using glibc version 2.1.3 and earlier, as well as specific versions of ISC BIND.
What type of attack can exploit CVE-2000-0335?
CVE-2000-0335 can be exploited by local attackers to spoof DNS query results, leading to potential data interception or redirection.
Is CVE-2000-0335 reversible?
CVE-2000-0335 cannot be reversed; the only effective solution is to upgrade to secure versions of the affected software.