---

SuSE Linux Advisory: postfix


SuSE Security Announcement

Package: postfix
Announcement-ID: SuSE-SA:2003:033
Date: Mon Aug 4 13:30:00 MEST 2003
Affected products: 7.2, 7.3, 8.0, 8.1
SuSE Linux Database Server
SuSE eMail Server III, 3.1
SuSE Linux Enterprise Server 7, 8
SuSE Linux Connectivity Server
SuSE Linux Office Server
SuSE Linux Openexchange Server
UnitedLinux 1.0
SuSE Linux Desktop 1.0
Vulnerability Type: remote Denial of Service (DoS) attack
Severity (1-10): 4
SuSE default package: Since SuSE Linux 8.1.
Cross References: CAN-2003-0468
CAN-2003-0540

Content of this advisory:

  1. security vulnerability resolved: remote DoS in postfix problem
    description, discussion, solution and upgrade information
  2. pending vulnerabilities, solutions, workarounds:
    • kernel
  3. standard appendix (further information)

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

Postfix is a flexible MTA replacement for sendmail. Michal
Zalewski has reported problems in postfix which can lead to a
remote DoS attack or allow attackers to bounce-scan private
networks. These problems have been fixed. Even though not all of
our products are vulnerable in their default configurations, the
updates should be applied.

In order for the update to take effect, you have to restart your
MTA by issuing the following command as root:

“/sbin/rcpostfix 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.

i386 Intel Platform:

SuSE-8.1:

ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/postfix-1.1.12-12.i586.rpm

4b3b65905911440051f869b3e95c2c66
patch rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/postfix-1.1.12-12.i586.patch.rpm

e73917624b5adfdbe113909135a50a42
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/postfix-1.1.12-12.src.rpm

0e5bcc6c3cd95f09c423cf00aac0c303

SuSE-8.0:

ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/postfix-1.1.12-13.i386.rpm

e0090e0ed051a532a62d787b020ac580
patch rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/postfix-1.1.12-13.i386.patch.rpm

8c156ca92ad4be83588041192efe5b60
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/postfix-1.1.12-13.src.rpm

f9389f00de109cea2f0b3b6c27f5a515

SuSE-7.3:

ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/postfix-20010228pl08-22.i386.rpm

1f4d3af8d10850096bc0260567caa334
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/postfix-20010228pl08-22.src.rpm

0ccc29a957609b3aeb2c12f3cc85284d

SuSE-7.2:

ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/postfix-20010228pl03-82.i386.rpm

444f983a8c8f0d18621a1e8b4c3dd260
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/postfix-20010228pl03-82.src.rpm

6d479bd0ed90bc7dc59a4201327ffc05

Sparc Platform:

SuSE-7.3:

ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/postfix-20010228pl08-15.sparc.rpm

83eb074dbcedae2c9947006b4c0411d2
source rpm(s):

ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/postfix-20010228pl08-15.src.rpm

ec7ae58e31fd2ec63ccd881454372307

PPC Power PC Platform:

SuSE-7.3:

ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/postfix-20010228pl08-36.ppc.rpm

f7b331c15b7bf705274afe2665e9e187
source rpm(s):

ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/postfix-20010228pl08-36.src.rpm

f2e5aa58e24599777a95dce715c3bcad


2) Pending vulnerabilities in SuSE Distributions and
Workarounds:

  • kernel Various bugs inside the kernel have been reported
    recently. The most important ones are

    • NFSv3 remote DoS
    • netfilter DoS
    • /proc infoleak
    • race condition in the ELF loader These bugs are fixed. The new
      kernel packages will be approved as soon as the testing is
      finished.

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.
  3. 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 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.
  4. 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:

    1. gpg is installed
    2. 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 ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de
      .
  • SuSE runs two security mailing lists to which any interested
    party may subscribe:

[email protected]

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

    <[email protected]>.

[email protected]

  • SuSE’s announce-only mailing list. Only SuSE’s security
    announcements are sent to this list. To subscribe, send an email to

    <[email protected]>.

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

<[email protected]>
or
<[email protected]>
respectively.


SuSE’s security contact is <[email protected]> or
<[email protected]>. The
<[email protected]>
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 <[email protected]>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <[email protected]>

Get the Free Newsletter!

Subscribe to Developer Insider for top news, trends, & analysis