Description:
Zack Weinberg discovered an insecure use of a predictable file name
[0] in the Python programming language [1]. Python attempts to execute
a file which is assumed to not exist just to find out what error
the operating system returns in this situation. It uses a constant
filename for this task which could lead to the execution of arbitrary
code. The Common Vulnerabilities and Exposures (CVE) project assigned
the id CAN-2002-1119 [2] to the problem.
Please check whether you are affected by running "<prefix>/bin/rpm -q
python". If you have the "python" 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], fetch it from the OpenPKG FTP service [6] or a mirror location,
verify its integrity [7], build a corresponding binary RPM from it [3]
and update your OpenPKG installation by applying the binary RPM [4].
For the release OpenPKG 1.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/1.1/UPD
ftp> get python-2.2.1-1.1.1.src.rpm
ftp> bye
$ <prefix>/bin/rpm -v --checksig python-2.2.1-1.1.1.src.rpm
$ <prefix>/bin/rpm --rebuild python-2.2.1-1.1.1.src.rpm
$ su -
# <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/python-2.2.1-1.1.1.*.rpm
________________________________________________________________________
For security reasons, this advisory was digitally signed with
the OpenPGP public key "OpenPKG <openpkg (at) openpkg (dot) org [email concealed]>" (ID 63C4CB9F)
of the OpenPKG project which you can find under the official URL
http://www.openpkg.org/openpkg.pgp or on http://keyserver.pgp.com/. To
check the integrity of this advisory, verify its digital signature by
using GnuPG (http://www.gnupg.org/). For instance, pipe this message to
the command "gpg --verify --keyserver keyserver.pgp.com".
________________________________________________________________________
Hash: SHA1
________________________________________________________________________
OpenPKG Security Advisory The OpenPKG Project
http://www.openpkg.org/security.html http://www.openpkg.org
openpkg-security (at) openpkg (dot) org [email concealed] openpkg (at) openpkg (dot) org [email concealed]
OpenPKG-SA-2003.006 23-Jan-2003
________________________________________________________________________
Package: python
Vulnerability: predictable filename allows arbitrary code execution
OpenPKG Specific: no
Affected Releases: Affected Packages: Corrected Packages:
OpenPKG CURRENT <= python-2.2.1-20020820 >= python-2.2.2-20021015
OpenPKG 1.2 none N.A.
OpenPKG 1.1 <= python-2.2.1-1.1.0 >= python-2.2.1-1.1.1
Affected Releases: Dependent Packages: none
Description:
Zack Weinberg discovered an insecure use of a predictable file name
[0] in the Python programming language [1]. Python attempts to execute
a file which is assumed to not exist just to find out what error
the operating system returns in this situation. It uses a constant
filename for this task which could lead to the execution of arbitrary
code. The Common Vulnerabilities and Exposures (CVE) project assigned
the id CAN-2002-1119 [2] to the problem.
Please check whether you are affected by running "<prefix>/bin/rpm -q
python". If you have the "python" 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], fetch it from the OpenPKG FTP service [6] or a mirror location,
verify its integrity [7], build a corresponding binary RPM from it [3]
and update your OpenPKG installation by applying the binary RPM [4].
For the release OpenPKG 1.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/1.1/UPD
ftp> get python-2.2.1-1.1.1.src.rpm
ftp> bye
$ <prefix>/bin/rpm -v --checksig python-2.2.1-1.1.1.src.rpm
$ <prefix>/bin/rpm --rebuild python-2.2.1-1.1.1.src.rpm
$ su -
# <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/python-2.2.1-1.1.1.*.rpm
________________________________________________________________________
References:
[0] http://mail.python.org/pipermail/python-dev/2002-August/027223.html
[1] http://www.python.org/
[2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-1119
[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.1/UPD/python-2.2.1-1.1.1.src.rpm
[6] ftp://ftp.openpkg.org/release/1.1/UPD/
[7] http://www.openpkg.org/security.html#signature
________________________________________________________________________
For security reasons, this advisory was digitally signed with
the OpenPGP public key "OpenPKG <openpkg (at) openpkg (dot) org [email concealed]>" (ID 63C4CB9F)
of the OpenPKG project which you can find under the official URL
http://www.openpkg.org/openpkg.pgp or on http://keyserver.pgp.com/. To
check the integrity of this advisory, verify its digital signature by
using GnuPG (http://www.gnupg.org/). For instance, pipe this message to
the command "gpg --verify --keyserver keyserver.pgp.com".
________________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Comment: OpenPKG <openpkg (at) openpkg (dot) org [email concealed]>
iD8DBQE+L8WAgHWT4GPEy58RAtl5AJ40nGCQKxI5yrs4KnKMaRI5veFM4ACePHmi
z8mwYutcBLXjOsWlMf5CEZM=
=OSaV
-----END PGP SIGNATURE-----
[ reply ]