SuSE Linux Advisory: radiusd-cistron
Jun 13, 2003, 15:56 (0 Talkback[s])
SuSE Security Announcement
||Friday, Jun 13th 2003 09:32 MET
||7.2, 7.3, 8.0
||possible remote system compromise
|SuSE default package:
Content of this advisory:
- security vulnerability resolved: handling too large NAS numbers
problem description, discussion, solution and upgrade
- pending vulnerabilities, solutions, workarounds:
- standard appendix (further information)
1) problem description, brief discussion, solution, upgrade
The package radiusd-cistron is an implementation of the RADIUS
protocol. Unfortunately the RADIUS server handles too large NAS
numbers not correctly. This leads to overwriting internal memory of
the server process and may be abused to gain remote access to the
system the RADIUS server is running on.
There is no temporary workaround known.
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.
Please note, missing packages will be published as soon as
Intel i386 Platform:
PPC Power PC Platform:
2) Pending vulnerabilities in SuSE Distributions and
- lprng A race condition in psbanner was fixed that can be abused
by local users to overwrite file owned by daemon:lp. New packages
are available on out FTP servers.
- frox The init script of frox handled tmp file in an insecure
manner. This behavior can be exploited by local users. New packages
are available on out FTP servers.
- poster A possible buffer overflow due to usage of gets() was
fixed which could have been exploited by malicious input data to
execute code under the user id of the user running poster. New
packages are available on out FTP servers.
- ghostscript-library Malicious PostScript[tm] files could
execute shell commands even if the ghostscript interpreter was
invoked with the -dSAFER flag.
3) standard appendix: authenticity verification, additional
- 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:
- md5sums as provided in the (cryptographically signed)
- using the internal gpg signatures of the rpm package.
- execute the command md5sum <name-of-the-file.rpm> 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@example.com), 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.
- rpm package signatures provide an easy way to verify the
authenticity of an rpm package. Use the command rpm -v --checksig
<file.rpm> to verify the signature of the package, where
<file.rpm> 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:
- gpg is installed
- 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 < announcement.txt |
gpg --import SuSE Linux distributions version 7.1 and thereafter
install the key "firstname.lastname@example.org"
upon installation or upgrade, provided that the package gpg is
installed. The file containing the public key is placed at the
top-level directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de
For general information or the frequently asked questions (faq)
send mail to:
SuSE's security contact is <email@example.com
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.
||SuSE Security Team <firstname.lastname@example.org>
||SuSE Package Signing Key <email@example.com>