[OpenPKG-SA-2004.046] OpenPKG Security Advisory (postgresql)

[OpenPKG <openpkg@xxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

________________________________________________________________________

OpenPKG Security Advisory                            The OpenPKG Project
http://www.openpkg.org/security.html              http://www.openpkg.org
openpkg-security@xxxxxxxxxxx                         openpkg@xxxxxxxxxxx
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

Description:
  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
  problem.

  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].

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

  $ ftp ftp.openpkg.org
  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
________________________________________________________________________

References:
  [0] http://www.postgresql.org/news/234.html 
  [1] http://www.postgresql.org/
  [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0977
  [3] http://www.openpkg.org/tutorial.html#regular-source
  [4] http://www.openpkg.org/tutorial.html#regular-binary
  [5] ftp://ftp.openpkg.org/release/2.2/UPD/postgresql-7.4.5-2.2.1.src.rpm
  [6] ftp://ftp.openpkg.org/release/2.1/UPD/postgresql-7.4.3-2.1.1.src.rpm
  [7] ftp://ftp.openpkg.org/release/2.2/UPD/
  [8] ftp://ftp.openpkg.org/release/2.1/UPD/
  [9] http://www.openpkg.org/security.html#signature
________________________________________________________________________

For security reasons, this advisory was digitally signed with the
OpenPGP public key "OpenPKG <openpkg@xxxxxxxxxxx>" (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@xxxxxxxxxxx>

iD8DBQFBglJmgHWT4GPEy58RAueIAKDP33ovouI34vd+CuiwPpaeTGPCCwCeOGZG
YdiADsf3fii2vRM4yl3mF1g=
=bMr1
-----END PGP SIGNATURE-----