[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20030915114903.GA22867@en4.engelschall.com>
From: openpkg at openpkg.org (OpenPKG)
Subject: [OpenPKG-SA-2003.038] OpenPKG Security Advisory (mysql)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
________________________________________________________________________
OpenPKG Security Advisory The OpenPKG Project
http://www.openpkg.org/security.html http://www.openpkg.org
openpkg-security@...npkg.org openpkg@...npkg.org
OpenPKG-SA-2003.038 15-Sep-2003
________________________________________________________________________
Package: mysql
Vulnerability: arbitrary code execution
OpenPKG Specific: no
Affected Releases: Affected Packages: Corrected Packages:
OpenPKG CURRENT <= mysql-4.0.14-20030904 >= mysql-4.0.15-20030910
OpenPKG 1.3 <= mysql-4.0.14-1.3.1 >= mysql-4.0.14-1.3.2
OpenPKG 1.2 <= mysql-3.23.54a-1.2.3 >= mysql-3.23.54a-1.2.4
Dependent Packages: none
Description:
Frank Denis reported a vulnerability [0] in MySQL [1] affecting MySQL3
versions 3.0.57 and earlier and MySQL4 versions 4.0.14 and earlier.
Passwords of MySQL users are stored in the "Password" field of the
"User" table, part of the "mysql" database. The passwords are hashed
and stored as a 16 characters long hexadecimal value. Unfortunately, a
function involved in password checking misses correct bounds checking.
By filling a "Password" field a value wider than 16 characters, a
buffer overflow will occur. The Common Vulnerabilities and Exposures
(CVE) project assigned the id CAN-2003-0780 [2] to the problem.
Please check whether you are affected by running "<prefix>/bin/rpm -q
mysql". If you have the "mysql" package installed and its version is
affected (see above), we recommend that you immediately upgrade it
(see Solution). [3][4]
Solution:
Select the updated source RPM appropriate for your OpenPKG release
[5][6], fetch it from the OpenPKG FTP service [7][8] or a mirror
location, verify its integrity [9], build a corresponding binary RPM
from it [3] and update your OpenPKG installation by applying the
binary RPM [4]. For the current release OpenPKG 1.3, perform the
following operations to permanently fix the security problem (for
other releases adjust accordingly).
$ ftp ftp.openpkg.org
ftp> bin
ftp> cd release/1.3/UPD
ftp> get mysql-4.0.14-1.3.2.src.rpm
ftp> bye
$ <prefix>/bin/rpm -v --checksig mysql-4.0.14-1.3.2.src.rpm
$ <prefix>/bin/rpm --rebuild mysql-4.0.14-1.3.2.src.rpm
$ su -
# <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/mysql-4.0.14-1.3.2.*.rpm
________________________________________________________________________
References:
[0] http://www.securityfocus.com/archive/1/337012/2003-09-05/2003-09-11/0
[1] http://www.mysql.com/
[2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0780
[3] http://www.openpkg.org/tutorial.html#regular-source
[4] http://www.openpkg.org/tutorial.html#regular-binary
[5] ftp://ftp.openpkg.org/release/1.2/UPD/mysql-3.23.54a-1.2.4.src.rpm
[6] ftp://ftp.openpkg.org/release/1.3/UPD/mysql-4.0.14-1.3.2.src.rpm
[7] ftp://ftp.openpkg.org/release/1.2/UPD/
[8] ftp://ftp.openpkg.org/release/1.3/UPD/
[9] http://www.openpkg.org/security.html#signature
________________________________________________________________________
For security reasons, this advisory was digitally signed with the
OpenPGP public key "OpenPKG <openpkg@...npkg.org>" (ID 63C4CB9F) of the
OpenPKG project which you can retrieve from http://pgp.openpkg.org and
hkp://pgp.openpkg.org. Follow the instructions on http://pgp.openpkg.org/
for details on how to verify the integrity of this advisory.
________________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Comment: OpenPKG <openpkg@...npkg.org>
iD8DBQE/ZabegHWT4GPEy58RAm2UAKDodjxqqZjLVRCxGaVAMURybF7ATwCdGM/p
6rOU5UPeEUK6fynl5TrS0l4=
=jZfi
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists