Bug 104501 - CAN-2003-0780 MySQL password field buffer overflow
CAN-2003-0780 MySQL password field buffer overflow
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: mysql (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Patrick Macdonald
David Lawrence
: Security
Depends On:
  Show dependency treegraph
Reported: 2003-09-16 10:49 EDT by Mark J. Cox
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-10-09 04:53:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2003:282 normal SHIPPED_LIVE Important: mysql security update 2003-10-09 00:00:00 EDT

  None (edit)
Description Mark J. Cox 2003-09-16 10:49:19 EDT
Frank Denis reported a bug in unpatched versions of MySQL versions prior to
3.0.58. Passwords of MySQL users are stored in the Password field of the
user table, part of the mysql database. By filling a Password field with a
value wider than 16 characters, a buffer overflow can occur. This could
allow an attacker who has the ability to modify the user table to execute
arbitrary code as the MySQL user. The Common Vulnerabilities and Exposures
project (cve.mitre.org) has assigned the name CAN-2003-0780 to this issue.
Comment 1 Patrick Macdonald 2003-09-16 10:55:38 EDT
We will address this by moving to MySQL 3.23.58 (released yesterday).
Comment 2 Mark J. Cox 2003-09-22 04:57:13 EDT
RHSA-2003:282 in progress
Comment 3 Mark J. Cox 2003-10-09 04:53:07 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.