Users login

Create an account »


Users login

Home » Hacking News » SuSE Security Announcement: imp (SuSE-SA:2003:0008)

SuSE Security Announcement: imp (SuSE-SA:2003:0008)

by Nikola Strahija on February 18th, 2003 Some SQL-injection vulnerabilities were found in IMP 2.x that allow an attacker to access the underlying database. No authentication is needed to exploit this bug.

Package: imp
Announcement-ID: SuSE-SA:2003:0008
Date: Tuesday, Feb. 18th 2003 18:20 MET
Affected products: 7.3, 8.0, 8.1
Vulnerability Type: remote system compromise
Severity (1-10): 3
SuSE default package: no
Cross References: CAN-2003-0025

Content of this advisory:
1) security vulnerability resolved: Multiple SQL-Injection
problem description, discussion, solution and upgrade information
2) pending vulnerabilities, solutions, workarounds:
- mod_php4
- libmcrypt
- vim
- pam_xauth
- openldap2
- mpg123
- syslinux
3) standard appendix (further information)


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

IMP is a well known PHP-based web-mail system.
Some SQL-injection vulnerabilities were found in IMP 2.x that
allow an attacker to access the underlying database. No authentication
is needed to exploit this bug.
An attacker can gain access to protected information or, in conjunction
with PostgreSQL, execute shell commands remotely.

There is no temporary fix known. Please install the new packages from
our FTP servers.

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.

Intel i386 Platform:

source rpm(s):

source rpm(s):

source rpm(s):

Sparc Platform:

source rpm(s):

AXP Alpha Platform:

PPC Power PC Platform:

source rpm(s):


2) Pending vulnerabilities in SuSE Distributions and Workarounds:

- mod_php4
A buffer overflow in the wordwrap() function has been reported.
New packages will be prepared and should be available on our ftp
servers soon.

- libmcrypt
Several buffer overflows in libmcrypt were discovered by Ilia
Alshanetsky. The buffer overflows can lead to system compromise.
New packages are currently being build.

- vim
Georgi Guninski reported a security problem
with vim's modeline support that allows the execution of commands
when a malformed file was opened. This bug may even be exploited
through MUAs like mutt.
We recommend to turn off this feature globally by adding the line:
set modelines=0
to the global configuration file /etc/vimrc. All currently supported
SuSE products are affected by this problem.
Modeline support is disabled by default in future version of SuSE

- openldap2
The BER decoding routines of the openldap2 packages for
SL 8.1 and SLES8 contained a bug which allowed remote attackers
to mount a DoS attack against vulnerable OpenLDAP servers. It is
necessary to update the openldap2-devel, openldap2-client and
openldap2 packages in order to prevent such attack.
New packages will be available on our FTP servers soon.

- mpg123
Our update directories on our ftp server for the SuSE Linux
distributions 7.3, 8.0 and 8.1 contain update packages for the mpg123
package. These updates fix a security problem with mpg123 that can
result in the execution of arbitrary commands upon playing a specially
crafted mpeg audio layer 3 file. Other versions of SuSE Linux than
mentioned above do not contain a vulnerable version of the mpg123 mp3

- pam_xauth
SuSE Linux starting with version 7.2 contain a PAM (Pluggable
Authentication Module) called pam_xauth which can be used to pass on
X11-authentification data (cookies, see "man Xsecurity") if a user
uses /bin/su to assume the privileges of another user. Since the
possession of the X11 authentification cookie grants access to the
running X-server and all of its resources, this should be considered a
security problem if the feature cannot be turned off by a non-root
user. The presence of the pam_xauth PAM does not represent a threat
such if it is not enabled by default.
By default, the pam_xauth module is not enabled in all SuSE products.
We recommend to use the /usr/X11R6/bin/sux wrapper script for the
su command that comes with SuSE products to pass on X11
authentification data if so desired intentionally by the user.

- syslinux
The syslinux bootloader has been found vulnerable to a not closely
named security weakness by Dan Hollis if the bootloader program is
installed setuid root.
We do not believe that elevated privileges are beneficial for a
bootloader. The packages in SuSE Linux are not vulnerable to the


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:

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 »