---

SuSE Linux Advisory: pptpd


SuSE Security Announcement

Package: pptpd
Announcement-ID: SuSE-SA:2003:029
Date: Fri Jun 6 16:30:00 MEST 2003
Affected products: 7.2, 7.3, 8.0, 8.1, 8.2
SuSE Linux Database Server
SuSE eMail Server III, 3.1
SuSE Linux Connectivity Server
SuSE Linux Enterprise Server 7
SuSE Linux Enterprise Server 8
SuSE Linux Office Server
UnitedLinux 1.0
Vulnerability Type: remote code execution
Severity (1-10): 5
SuSE default package: Yes
Cross References:

Content of this advisory:

  1. security vulnerability resolved: Remote code execution due to
    an integer overflow. problem description, discussion, solution and
    upgrade information
  2. pending vulnerabilities, solutions, workarounds:
    • snort
  3. standard appendix (further information)

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

The PPTP daemon contains a remotely exploitable buffer overflow
which was introduced due to a integer overflow in the third
argument passed to the read() library call. This bug has been
fixed. Since there is no workaround other than shutting down the
PPTP daemon an update is strongly recommended if you need a PPTP
server running.

To be sure the update takes effect you have to restart the PPTP
daemon by executing the following command as root:

“rcpptpd 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.2:

ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/pptpd-1.1.2-418.i586.rpm

5caa610c56180b7597886cd919362fb3
patch rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/pptpd-1.1.2-418.i586.patch.rpm

d28db868016ac2ce61fd7234a47d1502
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/pptpd-1.1.2-418.src.rpm

d69f971343f9d1cb5eef5f57ce16fffa

SuSE-8.1:

ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/pptpd-1.1.2-413.i586.rpm

be9e2f5a26fcf3f95bf9ffcc206e926c
patch rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/pptpd-1.1.2-413.i586.patch.rpm

448c505376cce08bdfa2e6b46f333db7
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/pptpd-1.1.2-413.src.rpm

067bd6274148e41b65d00e46674994a7

SuSE-8.0:

ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/pptpd-1.1.2-412.i386.rpm

60f1550b7f19cb9a6184dc60d43da431
patch rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/pptpd-1.1.2-412.i386.patch.rpm

870a38bd3256b196779e8e1e52cf2e5f
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/pptpd-1.1.2-412.src.rpm

78985af877c69ca16ee0ca652548aa79

SuSE-7.3:

ftp://ftp.suse.com/pub/suse/i386/update/7.3/n3/pptpd-1.1.2-412.i386.rpm

598676ca6ba8fad2cc79ca722a2387c4
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/pptpd-1.1.2-412.src.rpm

c5871ca7d894338530db9fc2882744c0

SuSE-7.2:

ftp://ftp.suse.com/pub/suse/i386/update/7.2/n3/pptpd-1.1.2-411.i386.rpm

89bd9ceacaad198b9436f6fc95433f04
source rpm(s):

ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/pptpd-1.1.2-411.src.rpm

96541c1e7ef7dfa6ce82ea4d3455e601

Sparc Platform:

SuSE-7.3:

ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n3/pptpd-1.1.2-132.sparc.rpm

5a868893c50a332b46fb50efd426db44
source rpm(s):

ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/pptpd-1.1.2-132.src.rpm

5654f0e078319165beee722d8250625d

PPC Power PC Platform:

SuSE-7.3:

ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n3/pptpd-1.1.2-262.ppc.rpm

6b8826e29930cfa077cfc6db18fd07f1
source rpm(s):

ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/pptpd-1.1.2-262.src.rpm

55208931a1240ca324fbefb155976bd6


2) Pending vulnerabilities in SuSE Distributions and
Workarounds:

  • snort A overflow in the stream4 preprocessor has been fixed in
    the new snort packages which will be available soon on our ftp
    servers.

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 security@suse.de), 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 “build@suse.de
      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:

suse-security@suse.com

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

    <suse-security-subscribe@suse.com>.

suse-security-announce@suse.com

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

        <suse-security-info@suse.com> or
        <suse-security-faq@suse.com> respectively.

SuSE’s security contact is <security@suse.com> or
<security@suse.de>. The
<security@suse.de>
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 <security@suse.de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>

Get the Free Newsletter!

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