What is the severity of CVE-2002-1146?

CVE-2002-1146 is considered a critical vulnerability due to its potential to cause buffer overflows, leading to remote code execution.

How do I fix CVE-2002-1146?

To fix CVE-2002-1146, upgrade the affected BIND or glibc libraries to versions that are not subject to this vulnerability.

Which systems are affected by CVE-2002-1146?

CVE-2002-1146 affects systems using BIND 4, BIND 8.2.x, and glibc versions up to and including 2.2.5.

What are the potential impacts of CVE-2002-1146?

The exploitation of CVE-2002-1146 can result in denial of service, data corruption, or unauthorized access to system resources.

How can I determine if my system is vulnerable to CVE-2002-1146?

You can determine if your system is vulnerable to CVE-2002-1146 by checking the installed versions of BIND and glibc against the vulnerable versions listed in the CVE.

Vulnerability/
CVE-2002-1146

medium

CWE

NVD-CWE-Other 119

11/10/2002

1/9/2004

8/8/2024

CVE-2002-1146: Buffer Overflow

First published: Fri Oct 11 2002(Updated: )

The BIND 4 and BIND 8.2.x stub resolver libraries, and other libraries such as glibc 2.2.5 and earlier, libc, and libresolv, use the maximum buffer size instead of the actual size when processing a DNS response, which causes the stub resolvers to read past the actual boundary ("read buffer overflow"), allowing remote attackers to cause a denial of service (crash).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GNU C Library (glibc)	<=2.2.5

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-1146?
CVE-2002-1146 is considered a critical vulnerability due to its potential to cause buffer overflows, leading to remote code execution.
How do I fix CVE-2002-1146?
To fix CVE-2002-1146, upgrade the affected BIND or glibc libraries to versions that are not subject to this vulnerability.
Which systems are affected by CVE-2002-1146?
CVE-2002-1146 affects systems using BIND 4, BIND 8.2.x, and glibc versions up to and including 2.2.5.
What are the potential impacts of CVE-2002-1146?
The exploitation of CVE-2002-1146 can result in denial of service, data corruption, or unauthorized access to system resources.
How can I determine if my system is vulnerable to CVE-2002-1146?
You can determine if your system is vulnerable to CVE-2002-1146 by checking the installed versions of BIND and glibc against the vulnerable versions listed in the CVE.

agent/references
agent/type
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/author
agent/last-modified-date
agent/description
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/gnu
product/glibc
canonical/gnu glibc
canonical/gnu c library (glibc)
version/gnu c library (glibc)/2.2.5

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2002-1146?
CVE-2002-1146 is considered a critical vulnerability due to its potential to cause buffer overflows, leading to remote code execution.
How do I fix CVE-2002-1146?
To fix CVE-2002-1146, upgrade the affected BIND or glibc libraries to versions that are not subject to this vulnerability.
Which systems are affected by CVE-2002-1146?
CVE-2002-1146 affects systems using BIND 4, BIND 8.2.x, and glibc versions up to and including 2.2.5.
What are the potential impacts of CVE-2002-1146?
The exploitation of CVE-2002-1146 can result in denial of service, data corruption, or unauthorized access to system resources.
How can I determine if my system is vulnerable to CVE-2002-1146?
You can determine if your system is vulnerable to CVE-2002-1146 by checking the installed versions of BIND and glibc against the vulnerable versions listed in the CVE.