What is the severity of CVE-1999-1330?

CVE-1999-1330 is classified as a moderate severity vulnerability due to the potential for buffer overflow attacks.

How do I fix CVE-1999-1330?

To fix CVE-1999-1330, you should update the db library to the latest version that implements snprintf properly.

What are the affected versions for CVE-1999-1330?

CVE-1999-1330 affects db library version 1.85.4, particularly on Debian Linux 4.0 and Red Hat Linux 4.2.

What is the potential impact of CVE-1999-1330?

The potential impact of CVE-1999-1330 includes the ability for attackers to execute arbitrary code through buffer overflows.

Is CVE-1999-1330 still a risk in modern systems?

CVE-1999-1330 is considered a historical vulnerability, but if legacy systems using affected software are still in use, they can remain at risk.

Vulnerability/
CVE-1999-1330

medium

4.6

CWE

NVD-CWE-Other 119

31/12/1999

9/3/2002

20/11/2024

CVE-1999-1330: Buffer Overflow

First published: Fri Dec 31 1999(Updated: )

The snprintf function in the db library 1.85.4 ignores the size parameter, which could allow attackers to exploit buffer overflows that would be prevented by a properly implemented snprintf.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Debian Debian Linux	=4.0
Red Hat Linux	=4.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-1999-1330?
CVE-1999-1330 is classified as a moderate severity vulnerability due to the potential for buffer overflow attacks.
How do I fix CVE-1999-1330?
To fix CVE-1999-1330, you should update the db library to the latest version that implements snprintf properly.
What are the affected versions for CVE-1999-1330?
CVE-1999-1330 affects db library version 1.85.4, particularly on Debian Linux 4.0 and Red Hat Linux 4.2.
What is the potential impact of CVE-1999-1330?
The potential impact of CVE-1999-1330 includes the ability for attackers to execute arbitrary code through buffer overflows.
Is CVE-1999-1330 still a risk in modern systems?
CVE-1999-1330 is considered a historical vulnerability, but if legacy systems using affected software are still in use, they can remain at risk.

agent/references
agent/type
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/description
agent/last-modified-date
agent/author
agent/event
agent/source
agent/softwarecombine
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/debian
product/debian linux
canonical/debian debian linux
vendor/redhat
product/linux
canonical/redhat linux
collector/nvd-index
version/debian debian linux/4.0
canonical/red hat linux
version/red hat linux/4.2

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-1999-1330?
CVE-1999-1330 is classified as a moderate severity vulnerability due to the potential for buffer overflow attacks.
How do I fix CVE-1999-1330?
To fix CVE-1999-1330, you should update the db library to the latest version that implements snprintf properly.
What are the affected versions for CVE-1999-1330?
CVE-1999-1330 affects db library version 1.85.4, particularly on Debian Linux 4.0 and Red Hat Linux 4.2.
What is the potential impact of CVE-1999-1330?
The potential impact of CVE-1999-1330 includes the ability for attackers to execute arbitrary code through buffer overflows.
Is CVE-1999-1330 still a risk in modern systems?
CVE-1999-1330 is considered a historical vulnerability, but if legacy systems using affected software are still in use, they can remain at risk.