What is the severity of CVE-2003-1331?

CVE-2003-1331 is considered a critical vulnerability due to its potential to allow local users to execute arbitrary code.

How do I fix CVE-2003-1331?

To fix CVE-2003-1331, you should update the MySQL client library to version 4.0.14 or later.

Who is affected by CVE-2003-1331?

CVE-2003-1331 affects local users of MySQL client library versions 4.0.13 and earlier.

Is CVE-2003-1331 a remote exploit?

No, CVE-2003-1331 is not a remote exploit; it is a local vulnerability that requires access to the affected system.

Vulnerability/
CVE-2003-1331

medium

CWE

NVD-CWE-Other 119

31/12/2003

25/6/2007

8/8/2024

CVE-2003-1331: Buffer Overflow

Q: What causes CVE-2003-1331?

CVE-2003-1331 is caused by a stack-based buffer overflow in the mysql_real_connect function due to a long socket name.

First published: Wed Dec 31 2003(Updated: )

Stack-based buffer overflow in the mysql_real_connect function in the MySql client library (libmysqlclient) 4.0.13 and earlier allows local users to execute arbitrary code via a long socket name, a different vulnerability than CVE-2001-1453.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
MySQL	<=4.0.9

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2003-1331?
CVE-2003-1331 is considered a critical vulnerability due to its potential to allow local users to execute arbitrary code.
How do I fix CVE-2003-1331?
To fix CVE-2003-1331, you should update the MySQL client library to version 4.0.14 or later.
Who is affected by CVE-2003-1331?
CVE-2003-1331 affects local users of MySQL client library versions 4.0.13 and earlier.
What causes CVE-2003-1331?
CVE-2003-1331 is caused by a stack-based buffer overflow in the mysql_real_connect function due to a long socket name.
Is CVE-2003-1331 a remote exploit?
No, CVE-2003-1331 is not a remote exploit; it is a local vulnerability that requires access to the affected system.

agent/references
agent/first-publish-date
agent/type
collector/mitre-cve
source/MITRE
agent/weakness
agent/author
agent/last-modified-date
agent/severity
agent/description
agent/event
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
agent/softwarecombine
vendor/oracle
canonical/mysql
version/mysql/4.0.9

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-2003-1331?
CVE-2003-1331 is considered a critical vulnerability due to its potential to allow local users to execute arbitrary code.
How do I fix CVE-2003-1331?
To fix CVE-2003-1331, you should update the MySQL client library to version 4.0.14 or later.
Who is affected by CVE-2003-1331?
CVE-2003-1331 affects local users of MySQL client library versions 4.0.13 and earlier.
What causes CVE-2003-1331?
CVE-2003-1331 is caused by a stack-based buffer overflow in the mysql_real_connect function due to a long socket name.
Is CVE-2003-1331 a remote exploit?
No, CVE-2003-1331 is not a remote exploit; it is a local vulnerability that requires access to the affected system.