lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
From: openpkg at (OpenPKG)
Subject: [OpenPKG-SA-2004.014] OpenPKG Security Advisory (mysql)

Hash: SHA1


OpenPKG Security Advisory                            The OpenPKG Project                   
OpenPKG-SA-2004.014                                          14-Apr-2004

Package:             mysql
Vulnerability:       insecure temporary file creation
OpenPKG Specific:    no

Affected Releases:   Affected Packages:        Corrected Packages:
OpenPKG CURRENT      <= mysql-4.0.18-20040214  >= mysql-4.0.18-20040414
OpenPKG 2.0          <= mysql-4.0.18-2.0.0     >= mysql-4.0.18-2.0.1
OpenPKG 1.3          <= mysql-4.0.14-1.3.2     >= mysql-4.0.14-1.3.3

Dependent Packages:  none

  Shaun Colley discovered [1] that the scripts "mysqlbug" and
  "mysqld_multi" of the MySQL RDBMS [0] perform insecure creations of
  temporary files. An attacker could create symbolic links in /tmp to
  achieve the overwriting of files with the privileges of the user
  invoking the scripts. The RDBMS startup wrapper "mysqld_multi" is
  currently not used in OpenPKG, although it is contained in the
  "mysql" package. The "mysqlbug" script could be run manually by the
  administrator. The Common Vulnerabilities and Exposures (CVE) project
  assigned the ids CAN-2004-0381 [2] and CAN-2004-0388 [3] to the

  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). [4][5]

  Select the updated source RPM appropriate for your OpenPKG release
  [6][7], fetch it from the OpenPKG FTP service [8][9] or a mirror
  location, verify its integrity [10], build a corresponding binary
  RPM from it [4] and update your OpenPKG installation by applying the
  binary RPM [5]. For the most recent release OpenPKG 2.0, perform the
  following operations to permanently fix the security problem (for
  other releases adjust accordingly).

  $ ftp
  ftp> bin
  ftp> cd release/2.0/UPD
  ftp> get mysql-4.0.18-2.0.1.src.rpm
  ftp> bye
  $ <prefix>/bin/openpkg rpm -v --checksig mysql-4.0.18-2.0.1.src.rpm
  $ <prefix>/bin/openpkg rpm --rebuild mysql-4.0.18-2.0.1.src.rpm
  $ su -
  # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/mysql-4.0.18-2.0.1.*.rpm


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 and
hkp:// Follow the instructions on
for details on how to verify the integrity of this advisory.

Comment: OpenPKG <>


Powered by blists - more mailing lists