lists.openwall.net | 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 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <OpenPKG-SA-2004.006@openpkg.org> From: openpkg at openpkg.org (OpenPKG) Subject: [OpenPKG-SA-2004.006] OpenPKG Security Advisory (uudeview) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ________________________________________________________________________ OpenPKG Security Advisory The OpenPKG Project http://www.openpkg.org/security.html http://www.openpkg.org openpkg-security@...npkg.org openpkg@...npkg.org OpenPKG-SA-2004.006 12-Mar-2004 ________________________________________________________________________ Package: uudeview Vulnerability: insecure temp file handling, buffer overflow OpenPKG Specific: no Affected Releases: Affected Packages: Corrected Packages: OpenPKG CURRENT <= uudeview-0.5.20-20040302 >= uudeview-0.5.20-20040312 OpenPKG 2.0 <= uudeview-0.5.19-2.0.0 >= uudeview-0.5.19-2.0.1 OpenPKG 1.3 <= uudeview-0.5.18-1.3.0 >= uudeview-0.5.18-1.3.1 Dependent Packages: none Description: Alerted by a posting on Bugtraq [1] the UUDeview [2] package was reviewed. It was found that 0.5.19 and later contains a bug which leads to failure retrieving the filename during decode. All versions suffered from insecure temporary file handling. Version 0.5.20 contains bug fixes for the parsing of header lines, exact handling of maximum line length and fixes for two buffer overflows which needed backporting. The corected packages listed above remedy all of these problems. Please check whether you are affected by running "<prefix>/bin/rpm -q uudeview". If you have the "uudeview" 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.0, 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.0/UPD ftp> get uudeview-0.5.19-2.0.1.src.rpm ftp> bye $ <prefix>/bin/openpkg rpm -v --checksig uudeview-0.5.19-2.0.1.src.rpm $ <prefix>/bin/openpkg rpm --rebuild uudeview-0.5.19-2.0.1.src.rpm $ su - # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/uudeview-0.5.19-2.0.1.*.rpm ________________________________________________________________________ References: [1] http://marc.theaimsgroup.com/?l=bugtraq&m=107789846720924 [2] http://www.fpx.de/fp/Software/UUDeview/ [3] http://www.openpkg.org/tutorial.html#regular-source [4] http://www.openpkg.org/tutorial.html#regular-binary [5] ftp://ftp.openpkg.org/release/1.3/UPD/uudeview-0.5.18-1.3.1.src.rpm [6] ftp://ftp.openpkg.org/release/2.0/UPD/uudeview-0.5.19-2.0.1.src.rpm [7] ftp://ftp.openpkg.org/release/1.3/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@...npkg.org>" (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@...npkg.org> iD8DBQFAUdQsgHWT4GPEy58RAlYkAKCeapN+4xx6Q2acF29Sr2ZxqCxPZgCeMsb/ Mc2nhcVu62xu1RQp65aa/Xk= =mu4H -----END PGP SIGNATURE-----
Powered by blists - more mailing lists