User: Password:
Subscribe / Log in / New account

OpenPKG alert OpenPKG-SA-2004.055 (gettext)

Hash: SHA1


OpenPKG Security Advisory                            The OpenPKG Project                   
OpenPKG-SA-2004.055                                          23-Dec-2004

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

Affected Releases:   Affected Packages:         Corrected Packages:
OpenPKG CURRENT      <= gettext-0.14.1-20041006 >= gettext-0.14.1-20041217
OpenPKG 2.2          <= gettext-0.14.1-2.2.0    >= gettext-0.14.1-2.2.1
OpenPKG 2.1          <= gettext-0.14.1-2.1.0    >= gettext-0.14.1-2.1.1

Affected Releases:   Dependent Packages:
OpenPKG CURRENT      aegis, apache, doodle, giftoxic, gimp, glib2, gpa,
                     gqview, gtk2, heartbeat, indent, kcd, kde-base,
                     kde-libs, kolab, libextractor, lyx, openjade,
                     orbit, papyrus, perl-locale, php, php5, popt,
                     smbc, subversion, xine-lib, xine-ui, yodl
OpenPKG 2.2          aegis, apache, giftoxic, gimp, glib2, gqview,
                     gtk2, indent, kolab, openjade, orbit, perl-locale,
                     php, popt, yodl
OpenPKG 2.1          aegis, apache, gimp, glib2, gqview, gtk2, indent,
                     kolab, openjade, orbit, perl-locale, php, popt, yodl

  Trustix security engineers discovered vulnerabilities [0] in the
  "autopoint" and "gettextize" scripts of GNU gettext [1]. The scripts
  in question insecurely generate temporary files which could allow
  a malicious user to overwrite another user's files via a "symlink
  attack". Software only using GNU gettext's headers and libraries is
  not affected by this problem, however. The Common Vulnerabilities and
  Exposures (CVE) project assigned the identifier CAN-2004-0966 [2] to
  the problem.

  Please check whether you are affected by running "<prefix>/bin/openpkg
  rpm -q gettext". If you have the "gettext" package installed and its
  version is affected (see above), we recommend that you immediately
  upgrade it (see Solution) and its dependent packages (see above) [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 gettext-0.14.1-2.2.1.src.rpm
  ftp> bye
  $ <prefix>/bin/openpkg rpm -v --checksig gettext-0.14.1-2.2.1.src.rpm
  $ <prefix>/bin/openpkg rpm --rebuild gettext-0.14.1-2.2.1.src.rpm
  $ su -
  # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/gettext-0.14.1-2.2.1.*.rpm

  Additionally, we recommend rebuilding and reinstalling all dependent
  packages (see above) as well [3][4].


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

The OpenPKG Project                          
Project Announcement List       

(Log in to post comments)

Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds