-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                samba
        Announcement-ID:        SUSE-SA:2004:035
        Date:                   Tuesday, Oct  5th 2004 16:53:01 MEST
        Affected products:      8.1, 8.2, 9.0
                                SUSE Linux Enterprise Server 8
                                SUSE Linux Desktop 1.0
        Vulnerability Type:     remote file disclosure
        Severity (1-10):        6
        SUSE default package:   Yes
        Cross References:       CAN-2004-0815

    Content of this advisory:
        1) security vulnerability resolved:
             - Samba file access problem
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
            - opera
            - kernel
            - mozilla
        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

    The Samba server, which allows to share files and resources via
    the SMB/CIFS protocol, contains a bug in the sanitation code of path
    names which allows remote attackers to access files outside of the
    defined share. In order to access these files, they must be readable
    by the account used for the SMB session.
    CAN-2004-0815 has been assigned to this issue.

2) solution/workaround

    As a temporary workaround you can set the
     wide links = no
    option in smb.conf and restart the samba server. However an update
    is recommended nevertheless.

3) special instructions and notes

    After successfully updating the samba package, you need to issue the
    following command as root:

      rcsmb restart

4) package location and checksums

    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.

    SUSE Linux 9.0:
          eb71869029b35d2a97d55e26514524db
    patch rpm(s):
          48bb3e455079fcfdf4ad2baa28f28557
    source rpm(s):
          d162ea5a39b14ee16ae1c6d5df9211bb

    SUSE Linux 8.2:
          79b0514a827bdd782e6d3f62bb92fb85
    patch rpm(s):
          a50dd448212245d51e9ac59ae50514e8
    source rpm(s):
          25d488678b607b3c67612ee065abd77a

    SUSE Linux 8.1:
          93d0fb2502f30593548dbe2f41ec8948
    patch rpm(s):
          da5b107fb71c5daf5972b6e0aaca4f5c
    source rpm(s):
          e0b9f9af6c5348cb9840b5d98a1c59dc


    x86-64 Platform:
    SUSE Linux 9.0:
          0f1c94aa23653b0cf9b318646d9153af
    patch rpm(s):
          569974c359702c263b0968ce8fb9810f
    source rpm(s):
          75c1a01d03af42835809691840eaa331

______________________________________________________________________________

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

     - opera
     New opera packages are available on our ftp servers, fixing
     CAN-2004-0691, CAN-2004-0597, CAN-2004-0598, CAN-2004-0599 and
     CAN-2004-0746.

     - kernel
     Update kernels for the kNFSd problem for SLES 8 and SL 8.1 have been
     released.

     - mozilla
     We are in the process of releasing updates for mozilla (and related
     browsers), fixing various issues: CAN-2004-0597, CAN-2004-0718,
     CAN-2004-0722, CAN-2004-0757, CAN-2004-0758, CAN-2004-0759,
     CAN-2004-0760, CAN-2004-0761, CAN-2004-0762, CAN-2004-0763,
     CAN-2004-0764 and CAN-2004-0765.
     We will give you concrete details in a separate mozilla advisory when
     the updates are available.


______________________________________________________________________________

6)  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-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
                .

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

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================