______________________________________________________________________________

                        SuSE Security Announcement

        Package:                libmcrypt
        Announcement-ID:        SuSE-SA:2003:0010
        Date:                   Wednesday, Feb. 26th 2003 11:20 MET
        Affected products:      7.1, 7.2, 7.3, 8.0, 8.1
                                SuSE eMail Server 3.1
                                SuSE eMail Server III
                                SuSE Linux Connectivity Server
                                SuSE Linux Enterprise Server 7
                                SuSE Linux Enterprise Server 8
                                SuSE Linux Office Server
        Vulnerability Type:     local privilege escalation
                                remote denial-of-service
        Severity (1-10):        3
        SuSE default package:   no
        Cross References:       CAN-2003-0031
                                CAN-2003-0032

    Content of this advisory:
        1) security vulnerability resolved: buffer overflow
           problem description, discussion, solution and upgrade information
        2) pending vulnerabilities, solutions, workarounds:
            - openssl
            - vnc
            - w3m
        3) standard appendix (further information)

______________________________________________________________________________

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

    Libmcrypt is a data encryption library that is able to load crypto-
    modules at run-time by using libltdl.
    Versions of libmcrypt prior to 2.5.5 include several buffer overflows
    that can be triggered by passing very long input to the mcrypt_*
    functions.
    The way libmcrypt handles dynamic crypto-modules via libltdl leads
    to memory-leaks that can cause a Denial-of-Service condition. This
    Problem can just be solved by linking modules static. This security
    update does not solve the memory-leak problem to avoid compatibility
    problems. Future releases of libmcrypt will be linked statically.

    To add the new library to the shared library cache you have to run
    ldconfig(8) as root. Additionally every program that is linked with
    libmcrypt needs to be restarted. ldd(1) can be used to find out which
    libraries are used by a program.
    Another way to determine which process uses a shared library that
    had been deleted is:
      lsof -n 2>/dev/null | grep RPMDELETE | cut -d " "  -f 1 | sort | uniq


    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:

    SuSE-8.1:
      
      6dc3127a069545b9cb00cafd9897021f
    patch rpm(s):
      
      3b88d2a7f1bf409ec6cdee4702c8dc40
    source rpm(s):
      
      8feed7301cb26aaa27084baea4a1677e

    SuSE-8.1:
      
      52bdf4a54df9fc698971fc1223b73d3d
    patch rpm(s):
      
      5ecc44d5b4d6f35a4f57db1d7092575e
    source rpm(s):
      
      8feed7301cb26aaa27084baea4a1677e

    SuSE-8.0:
      
      45997d80e97ce180a14b692b1f63b34b
    patch rpm(s):
      
      5ee228e095fbb3f53027a8a902978975
    source rpm(s):
      
      6c189dcf7bcbffa7f271cdeb9065e212

    SuSE-8.0:
      
      36b45ac7281a3dd2ba94794e26012180
    patch rpm(s):
      
      21ad28cb8dad5e418f0185b53470502c
    source rpm(s):
      
      6c189dcf7bcbffa7f271cdeb9065e212

    SuSE-7.3:
      
      f38972e593b79b8e22d5db86d9f75083
    source rpm(s):
      
      8390dbcef0b58b3cca5141254f3af8ea

    SuSE-7.3:
      
      6c5df7c177d88509aa10868142262868
    source rpm(s):
      
      8390dbcef0b58b3cca5141254f3af8ea

    SuSE-7.2:
      
      5ff561010a642a26f92b1a491df6317c
    source rpm(s):
      
      5430bf5ca7f79c16248024cbd6eb735a

    SuSE-7.2:
      
      7afa785605e65106a3a250bd166ca2ef
    source rpm(s):
      
      5430bf5ca7f79c16248024cbd6eb735a

    SuSE-7.1:
      
      4208d6905aa7c7dd13de30aa945f1693
    source rpm(s):
      
      d6c0a61d874869ee3927af3b58335ff4

    SuSE-7.1:
      
      03028dbcf99e6fe167a30cd9b2e6da0f
    source rpm(s):
      
      d6c0a61d874869ee3927af3b58335ff4



    Sparc Platform:

    SuSE-7.3:
      
      ae638ffb875f53df64325e8e0a148807
    source rpm(s):
      
      c6bdd14b370e0ca912e8ca7615580df0

    SuSE-7.3:
      
      846455cc24b212f7b7287332cababc06
    source rpm(s):
      
      c6bdd14b370e0ca912e8ca7615580df0



    AXP Alpha Platform:

    SuSE-7.1:
      
      3789bb0a9411d85ec4514490f342a70f
    source rpm(s):
      
      c8dd2a18ccb249ed384df14359ba094e

    SuSE-7.1:
      
      fa61fea31359365d07ccf45a56b1ca80
    source rpm(s):
      
      c8dd2a18ccb249ed384df14359ba094e



    PPC Power PC Platform:

    SuSE-7.3:
      
      f75b386d8894c98fd0fa534d3560abbe
    source rpm(s):
      
      5a3b3ce95652b81efb738b59aec1a7e4

    SuSE-7.3:
      
      6d3cea579e658b66ea62c97d4c58ce17
    source rpm(s):
      
      5a3b3ce95652b81efb738b59aec1a7e4

    SuSE-7.1:
      
      f097c1a2ce67b85cffb8f0076a6c09c3
    source rpm(s):
      
      9df0c47eb030905edeed919750aec9df

    SuSE-7.1:
      
      dc79a537365aae51c27d60dabb2615bf
    source rpm(s):
      
      9df0c47eb030905edeed919750aec9df

______________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

    - OpenSSL
      Update packages for the recently found weakness in the openssl package
      are available on our ftp servers. An announcement concerning this issue
      follows this announcement.

    - VNC
      VNC (Virtual Network Computing) uses a weak cookie generation process
      which can be exploited by an attacker to bypass authentication.
      New packages are currently being tested and will be available on our
      FTP servers soon.

    - w3m
      The textbased web-browser w3m does not properly escape HTML tags.
      A malicious HTML page or img alt attribute may lead to information
      leakage. New packages will be available 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
        md5sum 
       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.

    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.
       Prerequisites:
        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 "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   .


  - 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
        -   SuSE's announce-only mailing list.
            Only SuSE's security announcements are sent to this list.
            To subscribe, send an email to
                <suse-security-announce-subscribe@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>