<<< Date Index >>>     <<< Thread Index >>>

[OpenPKG-SA-2004.043] OpenPKG Security Advisory (tiff)



-----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.043                                          14-Oct-2004
________________________________________________________________________

Package:             tiff
Vulnerability:       arbitrary code execution
OpenPKG Specific:    no

Affected Releases:   Affected Packages:          Corrected Packages:
OpenPKG CURRENT      <= tiff-3.6.1-20040714      >= tiff-3.6.1-20041013
OpenPKG 2.1          <= tiff-3.6.1-2.1.0         >= tiff-3.6.1-2.1.1
OpenPKG 2.0          <= tiff-3.6.1-2.0.0         >= tiff-3.6.1-2.0.1

Affected Releases:   Dependent Packages:
OpenPKG CURRENT      cups emacs gdk-pixbuf gimp gtk2 imagemagick imlib
                     lcms lyx netpbm perl-tk povray scribus wx xemacs
                     xplanet xv

OpenPKG 2.1          emacs gdk-pixbuf gimp gtk2 imagemagick imlib lcms
                     netpbm perl-tk xv

OpenPKG 2.0          emacs gdk-pixbuf gimp gtk2 imagemagick imlib netpbm
                     perl-tk xv

Description:
  According to security advisory CESA-2004-006 from Chris Evans, the
  libtiff [0] image en-/decoder suffers from several heap based buffer
  overflows. The Common Vulnerabilities and Exposures (CVE) project
  assigned the id CAN-2004-0803 [1] to the problem.

  Other code reviewers found integer overflows which affect memory
  allocation. The Common Vulnerabilities and Exposures (CVE) project
  assigned the id CAN-2004-0886 [2] to the problem.

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

  Additionally, we recommend that you rebuild and reinstall
  all dependent packages (see above), if any, too [3][4].
________________________________________________________________________

References:
  [0] http://www.libtiff.org/
  [1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0803
  [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0886
  [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.1/UPD/tiff-3.6.1-2.1.1.src.rpm
  [6] ftp://ftp.openpkg.org/release/2.0/UPD/tiff-3.6.1-2.0.1.src.rpm
  [7] ftp://ftp.openpkg.org/release/2.1/UPD/
  [8] ftp://ftp.openpkg.org/release/2.0/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>

iD8DBQFBbr4HgHWT4GPEy58RAgTwAJ9GpzRv/XTwaL7T8QqB/jQgaJIFdgCeOSsW
W5KM345KbfAHGBTX1lmBUh8=
=CatT
-----END PGP SIGNATURE-----