Users login

Create an account »

JOIN XATRIX

Users login

Home » Hacking News » SuSE-SA:2002:029-wwwoffle

SuSE-SA:2002:029-wwwoffle

by Nikola Strahija on August 1st, 2002 Content of this advisory: 1) security vulnerability resolved: insufficient checking of Content Length value problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information)


1) problem description, brief discussion, solution, upgrade information

The WWWOFFLE, World Wide Web Offline Explorer, program suite acts as a
HTTP, FTP and Finger proxy to allow users with dial-up access to the
internet to do offline WWW browsing.

The parsing code of wwwoffled that processes HTTP PUT and POST requests
fails to handle a Content Length value smaller then -1. It is believed
that an attacker could exploit this bug to gain remote wwwrun access
to the system wwwoffled is running on.

The wwwoffle package is not installed by default.
As temporary workaround the wwwoffle daemon can be disabled the following
way (as root):
rcwwwoffle stop
If wwwoffled is started at boottime, you have to modify your boot
scripts too. This can be done by using the runlevel editor of yast2.

All running instances of wwwoffled need to be restarted after updating
your system (as root):
rcwwwoffle restart


Please download the update package for your distribution and verify its
integrity by the methods listed in section 3) of this announcement.
Then, install the package using the command "rpm -Fhv file.rpm" to apply
the update.
Our maintenance customers are being notified individually. The packages
are being offered to install from the maintenance web.

Missing packages will be published as soon as possible.



i386 Intel Platform:

SuSE-8.0

ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/wwwoffle-2.6d-300.i386.patch.rpm
841aed6738e45973891a08e8c666a624
SuSE-8.0
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/wwwoffle-2.6d-300.i386.rpm
de8e402d077da779070e3e1158b1463f
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/wwwoffle-2.6d-300.src.rpm
cb35aca6bfd20360883beb025647fabe

SuSE-7.3
ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/wwwoffle-2.6d-298.i386.rpm
08438c130e574eb2f3c9b7c8cc60f45b
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/wwwoffle-2.6d-298.src.rpm
1a48eda5d2b8032aef96c62cf2472cd1

SuSE-7.2
ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/wwwoffle-2.6b-63.i386.rpm
54ad9710b00030e5402478958545ad73
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/wwwoffle-2.6b-63.src.rpm
89705ac7a6ce27e8fb8198aef626315a

SuSE-7.1
ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/wwwoffle-2.6-20.i386.rpm
345aeaf33ed09e22cd0d5e2ea9202fef
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/wwwoffle-2.6-20.src.rpm
1c6a427d71b338a9c0091c4dc5ea1e61



Sparc Platform:

SuSE-7.1
ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/wwwoffle-2.6-18.sparc.rpm
b525c495f7e47f64cfbe1c364b683d90
source rpm:
ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/wwwoffle-2.6-18.src.rpm
ae9df7749fc38b0a7be2d013eeb5f8fb



AXP Alpha Platform:

SuSE-7.1
ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/wwwoffle-2.6-26.alpha.rpm
0140df0cf370942f50c9a6af2167b4bc
source rpm:
ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/wwwoffle-2.6-26.src.rpm
e2d72c3e70ef7e083fcd34a788cf1638



PPC Power PC Platform:

SuSE-7.3
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/wwwoffle-2.6d-207.ppc.rpm
98bfb93df81b987a93ba5ce8578325c2
source rpm:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/wwwoffle-2.6d-207.src.rpm
f8816a3a536a60b72839fe010b8aceeb

SuSE-7.1
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/wwwoffle-2.6-24.ppc.rpm
4a5f2eb327fa5441a7e9d0f9d0af32f5
source rpm:
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/wwwoffle-2.6-24.src.rpm
5a31460401e823a4adc17eda39222c1f



______________________________________________________________________________

2) Pending vulnerabilities in SuSE Distributions and Workarounds:

- bzip
The FreeBSD Team discovered some security related bugs in bzip2.
By exploiting this bugs an attacker could change file permissions or
overwrite files.
Bzip got fixed and a new version of the bzip package is available
on our FTP servers.

- pam_ldap
A "format string" bug in pam_ldap's logging functions gots fixed.
New packages are available on our FTP servers.

- chfn/util-linux
Linux distributors have published security announcements about password
locking race conditions that lead to a local root vulnerability.
SuSE products are not affected by this weakness because we use the
user/group management utilities from the shadow package. These utilities
are not affected.


- libpng
libpng is a library that provides functions for applications to handle
PNG image files (Portable Network Graphics). An overflow vulnerability
has been found in the libpng library that may make it possible for an
attacker to run arbitrary code or to crash an application that uses
the libpng library if the application in question opens a png image file.
We are in the process of fixing this vulnerability.


______________________________________________________________________________

3) standard appendix: authenticity verification, additional information

- Package authenticity verification:

SuSE update packages are available on many mirror ftp servers all over
the world. While this service is being considered valuable and important
to the free and open source software community, many users wish to be
sure about the origin of the package and its content before installing
the package. There are two verification methods that can be used
independently from each other to prove the authenticity of a downloaded
file or rpm package:
1) md5sums as provided in the (cryptographically signed) announcement.
2) using the internal gpg signatures of the rpm package.

1) execute the command
md5sum
after you downloaded the file from a SuSE ftp server or its mirrors.
Then, compare the resulting md5sum with the one that is listed in the
announcement. Since the announcement containing the checksums is
cryptographically signed (usually using the key [email protected]),
the checksums show proof of the authenticity of the package.
We disrecommend to subscribe to security lists which cause the
email message containing the announcement to be modified so that
the signature does not match after transport through the mailing
list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless.

2) rpm package signatures provide an easy way to verify the authenticity
of an rpm package. Use the command
rpm -v --checksig
to verify the signature of the package, where is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an un-installed rpm
package file.
Prerequisites:
a) gpg is installed
b) The package is signed using a certain key. The public part of this
key must be installed by the gpg program in the directory
~/.gnupg/ under the user's home directory who performs the
signature verification (usually root). You can import the key
that is used by SuSE in rpm packages for SuSE Linux by saving
this announcement to a file ("announcement.txt") and
running the command (do "su -" to be root):
gpg --batch; gpg .

[email protected]
- SuSE's announce-only mailing list.
Only SuSE's security announcements are sent to this list.
To subscribe, send an email to
.

For general information or the frequently asked questions (faq)
send mail to:
or
respectively.

=====================================================================
SuSE's security contact is or .
The public key is listed below.
=====================================================================
______________________________________________________________________________

The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular,
it is desired that the clear-text signature shows proof of the
authenticity of the text.
SuSE Linux AG makes no warranties of any kind whatsoever with respect
to the information contained in this security advisory.

Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key


Newsletter signup

Signup to our monthly newsletter and stay in touch with IT news!

Free E-books

We've got ebooks! But they're not online. :( Please give us a few days to bring downloads back.

Contact

Have something to say or just wanna drop us a line? Please keep this in mind: to spam, we reply with spam.

Contact us »