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.046] OpenPKG Security Advisory (postgresql)

Hash: SHA1


OpenPKG Security Advisory                            The OpenPKG Project                   
OpenPKG-SA-2004.046                                          29-Oct-2004

Package:             postgresql
Vulnerability:       insecure temporary file generation
OpenPKG Specific:    no

Affected Releases:   Affected Packages:           Corrected Packages:
OpenPKG CURRENT      <= postgresql-7.4.5-20041028 >= postgresql-7.4.6-20041028
OpenPKG 2.2          <= postgresql-7.4.5-2.2.0    >= postgresql-7.4.5-2.2.1
OpenPKG 2.1          <= postgresql-7.4.3-2.1.0    >= postgresql-7.4.3-2.1.1

Dependent Packages:  none

  According to a vendor announcement [0], a vulnerability exists in
  the generation of temporary files in the PostgreSQL RDBMS [1]. The
  issue exists in the "make_oidjoins_check" script creating temporary
  files insecurely and possibly allowing a malicious user to overwrite
  another user's files via a symlink attack. The Common Vulnerabilities
  and Exposures (CVE) project assigned the id CAN-2004-0977 [2] to the

  Please check whether you are affected by running "<prefix>/bin/openpkg
  rpm -q postgresql". If you have the "postgresql" package installed and
  its version is affected (see above), we recommend that you immediately
  upgrade it (see Solution) [3][4].

  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 most recent release OpenPKG 2.2, perform the
  following operations to permanently fix the security problem (for
  other releases adjust accordingly).

  $ ftp
  ftp> bin
  ftp> cd release/2.2/UPD
  ftp> get postgresql-7.4.5-2.2.1.src.rpm
  ftp> bye
  $ <prefix>/bin/openpkg rpm -v --checksig postgresql-7.4.5-2.2.1.src.rpm
  $ <prefix>/bin/openpkg rpm --rebuild postgresql-7.4.5-2.2.1.src.rpm
  $ su -
  # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/postgresql-7.4.5-2.2.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