head 1.4; access; symbols; locks; strict; comment @# @; 1.4 date 2005.12.03.12.19.40; author rse; state Exp; branches; next 1.3; commitid qqpAOapyuzxSmacr; 1.3 date 2005.12.03.11.50.04; author rse; state Exp; branches; next 1.2; commitid irQCXvyd7wvJcacr; 1.2 date 2003.09.15.11.49.29; author rse; state Exp; branches; next 1.1; 1.1 date 2003.09.15.11.33.39; author thl; state Exp; branches; next ; desc @@ 1.4 log @resign after latest adjustments @ text @-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ________________________________________________________________________ OpenPKG Security Advisory The OpenPKG Project http://www.openpkg.org/security.html http://www.openpkg.org openpkg-security@@openpkg.org openpkg@@openpkg.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 CVE-2003-0780 [2] to the problem. Please check whether you are affected by running "/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 $ /bin/rpm -v --checksig mysql-4.0.14-1.3.2.src.rpm $ /bin/rpm --rebuild mysql-4.0.14-1.3.2.src.rpm $ su - # /bin/rpm -Fvh /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=CVE-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 " (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 iD8DBQFDkYzRgHWT4GPEy58RAu/VAJ9hZadsovvksTDk6B2edOErCkjFxgCcCmVO qiPpjCB0B88yiYBYEAIgr28= =ySRM -----END PGP SIGNATURE----- @ 1.3 log @switch to newer world order of CVE instead of CAN and where no more solution hints are specified in detail and anybody should already memorize this standard text @ text @d78 1 d82 3 a84 3 iD8DBQE/ZabegHWT4GPEy58RAm2UAKDodjxqqZjLVRCxGaVAMURybF7ATwCdGM/p 6rOU5UPeEUK6fynl5TrS0l4= =jZfi @ 1.2 log @final polishing and signing of MySQL SA @ text @d32 1 a32 1 (CVE) project assigned the id CAN-2003-0780 [2] to the problem. d62 1 a62 1 [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0780 @ 1.1 log @SA-2003.038-mysql; CAN-2003-0780 @ text @d1 3 d9 1 a9 1 OpenPKG-SA-2003.mysql 15-Sep-2003 d24 9 a32 11 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 "User" table, part of the "mysql" database, specifically in the "Password" field. The passwords are hashed and stored as a 16 characters long hexadecimal value, specifically in the "Password" field. 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. d43 4 a46 4 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). d78 2 d81 4 @