Users login

Create an account »


Users login

Home » Hacking News » SuSE-SA:2002:043-traceroute-nanog/nkitb


by Nikola Strahija on November 13th, 2002 Content of this advisory: 1) security vulnerability resolved: - dropping root after gaining raw socket - a few buffer overflows 2) pending vulnerabilities, solutions, workarounds: - ypserv - horde - openssh - wrong MD5 sums in advisory SuSE-SA:2002:041 3) standard appendix (further information)

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

Traceroute is a tool that can be used to track packets in a TCP/IP
network to determine it's route or to find out about not working
Traceroute-nanog requires root privilege to open a raw socket. It
does not relinquish these privileges after doing so. This allows
a malicious user to gain root access by exploiting a buffer
overflow at a later point.

For all products prior to 8.1, the traceroute package
contains the NANOG implementation. This package is installed by
default. Starting with 8.1, SuSE Linux contains a traceroute program
rewritten by Olaf Kirch that does not require root privileges anymore.
This version of traceroute is not vulnerable.

This is the first update for the traceroute package on the SuSE Linux
distributions 7.1 through 8.0. We have changed the version string in
the update packages to read "6.x" instead of the former "nanog_6.x" to
enable a clean comparison between version numbers. This change is
misleading in that it suggests that the package name has been changed.
Since only the version string is affected, the name of the package
remains the same.

As a workaround you can remove the setuid bit or just allow trusted
users to execute traceroute-nanog.
Become root and add the following line to /etc/permissions.local:
"/usr/sbin/traceroute root.trusted 4750"
This line will keep the setuid root bit for /usr/sbin/traceroute
and just allow users in group trusted to execute the binary.
To make the permission change and keep it permanent you have to
run chkstat(8):
"chkstat -set /etc/permissions.local"

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 are being built and tested and will be available for
download soon.

Intel i386 Platform:

source rpm(s):

source rpm(s):

source rpm(s):

source rpm(s):

source rpm(s):

Sparc Platform:

source rpm(s):

AXP Alpha Platform:

source rpm(s):

source rpm(s):

PPC Power PC Platform:

source rpm(s):

source rpm(s):

source rpm(s):


2) Pending vulnerabilities in SuSE Distributions and Workarounds:

- horde
There was a cross-site scripting vulnerability in horde.
Updated packages have been released for 7.3, 8.0 and 8.1.

- openssh
When the SSH daemon finds that a user's password has expired,
the user is forced to set a new password. While doing so, sshd
did not turn off the terminal echo, causing the password to
be visible on the screen as it was typed. We are in the process
of releasing updated package for 7.0 through 7.3. SuSE Linux 8.0
and 8.1 are not affected.

- ypserv
Thorsten Kukuk found a memory leak in ypserv that caused it to lose
small amounts of memory each time it processes certain malformed
requests. This could be used by an attacker to kill ypserv by repeating
this exercise until it runs out of memory.
We have released updated packages for 7.0 through 8.0. SuSE Linux 8.1
is not affected.

- wrong MD5 sums in advisory SuSE-SA:2002:041
Due to a mistake the SuSE Security Announcement SuSE-SA:2002:041
(perl-Mailtools) contains wrong MD5 sums.
A new version will be published on our security web sites soon.


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
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.
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 < announcement.txt | gpg --import
SuSE Linux distributions version 7.1 and thereafter install the
key "[email protected]" 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 .

- SuSE runs two security mailing lists to which any interested party may

[email protected]
- general/linux/SuSE security discussion.
All SuSE security announcements are sent to this list.
To subscribe, send an email to

[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:

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.

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.


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

Contact us »