[<prev] [next>] [day] [month] [year] [list]
Message-ID: <OpenPKG-SA-2005.003__895.16449156708$1105983497$gmane$org@openpkg.org>
Date: Mon, 17 Jan 2005 13:37:28 +0100
From: OpenPKG <openpkg@...npkg.org>
To: bugtraq@...urityfocus.com
Subject: [OpenPKG-SA-2005.003] OpenPKG Security Advisory (a2ps)
-----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-2005.003 17-Jan-2005
________________________________________________________________________
Package: a2ps
Vulnerability: arbitrary code execution
OpenPKG Specific: no
Affected Releases: Affected Packages: Corrected Packages:
OpenPKG CURRENT <= a2ps-4.13b-20040818 >= a2ps-4.13b-20050117
OpenPKG 2.2 <= a2ps-4.13b-2.2.0 >= a2ps-4.13b-2.2.1
OpenPKG 2.1 <= a2ps-4.13b-2.1.0 >= a2ps-4.13b-2.1.1
Dependent Packages: none
Description:
Rudolf Polzer discovered [0] a vulnerability in GNU a2ps [1], a
converter and pretty-printer for many formats to PostScript. The
program does not escape shell meta characters properly which could
lead to the execution of arbitrary commands as a privileged user if
a2ps is installed as a printer filter. a2ps allows remote attackers to
execute arbitrary commands via shell metacharacters in the filename.
The Common Vulnerabilities and Exposures (CVE) project assigned the
identifier CAN-2004-1170 [2] to the problem.
Please check whether you are affected by running "<prefix>/bin/openpkg
rpm -q a2ps". If you have the "a2ps" 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 a2ps-4.13b-2.2.1.src.rpm
ftp> bye
$ <prefix>/bin/openpkg rpm -v --checksig a2ps-4.13b-2.2.1.src.rpm
$ <prefix>/bin/openpkg rpm --rebuild a2ps-4.13b-2.2.1.src.rpm
$ su -
# <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/a2ps-4.13b-2.2.1.*.rpm
________________________________________________________________________
References:
[0] http://archives.neohapsis.com/archives/fulldisclosure/2004-08/1026.html
[1] http://www.inf.enst.fr/~demaille/a2ps/
[2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1170
[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/a2ps-4.13b-2.2.1.src.rpm
[6] ftp://ftp.openpkg.org/release/2.1/UPD/a2ps-4.13b-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@...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>
iD8DBQFB67F5gHWT4GPEy58RAiuUAKCaVwm6qztuFo7Gx7aZP6ZrITKjgQCfdGrL
ZrkstKQlbfIuKDISsjhjYHE=
=+cr1
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists