Users login

Create an account »


Users login

Home » Hacking News » SuSE-SA:2002:012-ucdsnmp


by Nikola Strahija on April 9th, 2002 Content of this advisory: 1) security vulnerability resolved: serveral bugs in ucdsnmp 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 Secure Programming Group of the Oulu University, Sweden released
a testing suite for SNMP implementations. Several bugs could be triggered
in the ucd-snmpd code by using this testing suite. These bugs lead to
remote denial-of-service attacks and may possibly exploited to break
system security remotely.
Additionally, the SuSE Security Team did a full audit of the ucd-snmpd
code and we hope to avoid more problems caused by other bugs in the

Generally SNMP access (UDP 161,162) and all UDP bouncing services like
echo (UDP 7) should completely be blocked at your firewall.

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.

After updateing the RPM package run "ldconfig" and "rcsnmpd restart"
as root to make the new library effective and to start the new daemon.

Please note! We made a version upgrade of ucdsnmp, so other
programs that rely on the ucdsnmpd library may become broken.
We are aware of the following dependencies:
- ethereal
- gxsnmp
- mod_php4
- snmp
- tngfw
New RPM packages for this programs will be released as soon as possible.

The mod_php4 packages have been published and require the new ucdsnmp

i386 Intel Platform:

source rpm:

source rpm:

source rpm:

source rpm:

source rpm:

Sparc Platform:

source rpm:

source rpm:

source rpm:

AXP Alpha Platform:

source rpm:

source rpm:

source rpm:

PPC PowerPC Platform:

source rpm:

source rpm:

source rpm:

source rpm:


2) Pending vulnerabilities in SuSE Distributions and Workarounds:

- inn
update packages are available for the inn news server, as contained
in all SuSE Linux products. The updates fix a problem where the
inews program wouldn't properly check the moderator's email address
that is supplied by the server. The user calling inews may gain
elevated local privileges with this bug.
In addition to the fix for this particular bug, minor directory
permission adaptions have been made.
We will not release an own security announcement for this bug.

- gnokii for SuSE-7.2 and SuSE-7.3
The gnokii package for the SuSE Linux distributions contain a
vulnerability that allows write access to any file on the system,
allowing a local attacker to gain root privileges. Update packages
for the SuSE Linux Distributions 7.2 and 7.3 are avbailable on our ftp
server that fix this problem.
We will not release an own security announcement for this bug.

- mod_php4 for SuSE Linux 7.2
A packaging error caused the update packages for the mod_php4 package
on SuSE Linux 7.2 to lack support for TTF, XML and IMAP. This has been
corrected with new update packages on the ftp server.

- fileutils
A race condition while recursively removing directory structures from
world-writeable directories cause the rm(1) command to be vulnerable
to an attack that allows a local user to remove arbitrary directories
(and files) from the system. The error has been corrected in the
update packages that are available from the a1/ series update
directrory of each distribution. Users of SuSE Linux Enterprise
Server 7 based products receive their update packages through the
SuSE maintenance web.
We will not release an own security announcement for this bug.

- nscd
The name service cache daemon shipped with supported SuSE products
(part of the glibc/shlibs package) is configured to run by default,
but configured to not cache hosts entries (A- and PTR records from
domain name servers). Therefore, a vulnerability that takes advantage
of the fact that nscd uses an existing (cached) PTR record for
resolving a request for an A-record is not applicable to SuSE
products. The weakness will be fixed in future releases of SuSE products.


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 uninstalled 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 .

[email protected]
- SuSE's announce-only mailing list.
Only SuSE's security annoucements 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 cleartext 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

Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see

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 »