-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                asterisk
        Announcement ID:        SUSE-SA:2006:069
        Date:                   Thu, 16 Nov 2006 18:00:00 +0000
        Affected Products:      SUSE LINUX 10.1
                                SUSE LINUX 10.0
                                SUSE LINUX 9.3
        Vulnerability Type:     remote denial of service
        Severity (1-10):        6
        SUSE Default Package:   no
        Cross-References:       CVE-2006-5444, CVE-2006-5445

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             Asterisk two security problems
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            See SUSE Security Summary Report.
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   Two security problem have been found and fixed in the PBX software
   Asterisk.

   CVE-2006-5444: Integer overflow in the get_input function in the
   Skinny channel driver (chan_skinny.c) as used by Cisco SCCP phones,
   allows remote attackers to potentially execute arbitrary code via a
   certain dlen value that passes a signed integer comparison and leads
   to a heap-based buffer overflow.

   CVE-2006-5445: A vulnerability in the SIP channel driver
   (channels/chan_sip.c) in Asterisk on SUSE Linux 10.1 allows remote
   attackers to cause a denial of service (resource consumption)
   via unspecified vectors that result in the creation of "a real pvt
   structure" that uses more resources than necessary.

2) Solution or Work-Around

   There is no known workaround, please install the update packages.

3) Special Instructions and Notes

   Please close and restart all running instances of asterisk after the update.

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.


   x86 Platform:

   SUSE LINUX 10.1:
             8af646c3a835f9388bb24cf4fb4f4896

   SUSE LINUX 10.0:
             1ea65f3361d4968a7d56ad5db441da83

   SUSE LINUX 9.3:
             394149307b5165453749dac1677705d5

   Power PC Platform:

   SUSE LINUX 10.1:
             3c265f83a0329dd1a4b2391f0c479d65

   SUSE LINUX 10.0:
             9b1ae15d6248aeb79d68058fe924cba9

   x86-64 Platform:

   SUSE LINUX 10.1:
             372cf1854c36e1c347f8d349a0025e63

   SUSE LINUX 10.0:
             9ed9cc0cb929b73e2c93485762dfa778

   SUSE LINUX 9.3:
             3c5340048f204d6111f0be16fcf40923

   Sources:

   SUSE LINUX 10.1:
             835aad905134159f86e8905ba9adfcc6

   SUSE LINUX 10.0:
             503bcc2cbd1559a8e012b1cebe7af889

   SUSE LINUX 9.3:
             c89bb1617fed47b62d6ad1208f1b6c69

______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   See SUSE Security Summary Report.
______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    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) Using the internal gpg signatures of the rpm package
    2) MD5 checksums as provided in this announcement

    1) The internal 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, replacing  with the
       filename of the RPM package downloaded. The package is unmodified if it
       contains a valid signature from build@suse.de with the key ID 9C800ACA.

       This key is automatically imported into the RPM database (on
       RPMv4-based distributions) and the gpg key ring of 'root' during
       installation. You can also find it on the first installation CD and at
       the end of this announcement.

    2) If you need an alternative means of verification, use the md5sum
       command to verify the authenticity of the packages. 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
       SUSE security announcement. Because the announcement containing the
       checksums is cryptographically signed (by security@suse.de), the
       checksums show proof of the authenticity of the package if the
       signature of the announcement is valid. Note that the md5 sums
       published in the SUSE Security Announcements are valid for the
       respective packages only. Newer versions of these packages cannot be
       verified.

  - SUSE runs two security mailing lists to which any interested party may
    subscribe:

    suse-security@suse.com
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail 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 e-mail to
                .

    For general information or the frequently asked questions (FAQ),
    send mail to  or
    .

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