Description:
According to Hironori Sakamoto, one of the w3m developers, two
security vulnerabilities exist in w3m [0]. Releases before 0.3.2.1
do not escape an HTML tag in a frame, which allows remote attackers
to access files or cookies [1]. Releases before 0.3.2.2 do not
properly escape HTML tags in the ALT attribute of an IMG tag, which
could allow remote attackers to access files or cookies [2]. The
Common Vulnerabilities and Exposures (CVE) project assigned the ids
CAN-2002-1335 [3] and CAN-2002-1348 [4] to these problems. We have
backported the patch to the 0.3.1 release.
Please check whether you are affected by running "<prefix>/bin/rpm
-q w3m". If you have the "w3m" package installed and its version is
affected (see above), we recommend that you immediately upgrade it
(see Solution) [5][6].
Solution:
Select the updated source RPM appropriate for your OpenPKG release
[7], fetch it from the OpenPKG FTP service [8] or a mirror location,
verify its integrity [9], build a corresponding binary RPM from it [5]
and update your OpenPKG installation by applying the binary RPM [6].
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 w3m-0.3.1-1.1.1.src.rpm
ftp> bye
$ <prefix>/bin/rpm -v --checksig w3m-0.3.1-1.1.1.src.rpm
$ <prefix>/bin/rpm --rebuild w3m-0.3.1-1.1.1.src.rpm
$ su -
# <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/w3m-0.3.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.009 18-Feb-2003
________________________________________________________________________
Package: w3m
Vulnerability: cookie information leak
OpenPKG Specific: no
Affected Releases: Affected Packages: Corrected Packages:
OpenPKG CURRENT <= w3m-0.3.2.1-20021126 >= w3m-0.3.2.2-20021205
OpenPKG 1.2 N.A. >= w3m-0.3.2.2-1.2.0
OpenPKG 1.1 <= w3m-0.3.1-1.1.0 >= w3m-0.3.1-1.1.1
Affected Releases: Dependent Packages: none
Description:
According to Hironori Sakamoto, one of the w3m developers, two
security vulnerabilities exist in w3m [0]. Releases before 0.3.2.1
do not escape an HTML tag in a frame, which allows remote attackers
to access files or cookies [1]. Releases before 0.3.2.2 do not
properly escape HTML tags in the ALT attribute of an IMG tag, which
could allow remote attackers to access files or cookies [2]. The
Common Vulnerabilities and Exposures (CVE) project assigned the ids
CAN-2002-1335 [3] and CAN-2002-1348 [4] to these problems. We have
backported the patch to the 0.3.1 release.
Please check whether you are affected by running "<prefix>/bin/rpm
-q w3m". If you have the "w3m" package installed and its version is
affected (see above), we recommend that you immediately upgrade it
(see Solution) [5][6].
Solution:
Select the updated source RPM appropriate for your OpenPKG release
[7], fetch it from the OpenPKG FTP service [8] or a mirror location,
verify its integrity [9], build a corresponding binary RPM from it [5]
and update your OpenPKG installation by applying the binary RPM [6].
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 w3m-0.3.1-1.1.1.src.rpm
ftp> bye
$ <prefix>/bin/rpm -v --checksig w3m-0.3.1-1.1.1.src.rpm
$ <prefix>/bin/rpm --rebuild w3m-0.3.1-1.1.1.src.rpm
$ su -
# <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/w3m-0.3.1-1.1.1.*.rpm
________________________________________________________________________
References:
[0] http://w3m.sourceforge.net/
[1] http://mi.med.tohoku.ac.jp/~satodai/w3m-dev-en/200211.month/838.html
[2] http://mi.med.tohoku.ac.jp/~satodai/w3m-dev-en/200212.month/843.html
[3] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-1335
[4] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-1348
[5] http://www.openpkg.org/tutorial.html#regular-source
[6] http://www.openpkg.org/tutorial.html#regular-binary
[7] ftp://ftp.openpkg.org/release/1.1/UPD/w3m-0.3.1-1.1.1.src.rpm
[8] ftp://ftp.openpkg.org/release/1.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 (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+UijXgHWT4GPEy58RAmIIAJ9EmK4PGY36CKa5yGJkUHUQN0mzfACdE4GJ
vO43TJW7bwzDxDWOKu9jH4I=
=lrjv
-----END PGP SIGNATURE-----
[ reply ]