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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                asterisk
        Announcement ID:        SUSE-SA:2007:034
        Date:                   Wed, 06 Jun 2007 18:00:00 +0000
        Affected Products:      SUSE LINUX 10.1
                                openSUSE 10.2
        Vulnerability Type:     remote denial of service
        Severity (1-10):        6
        SUSE Default Package:   no
        Cross-References:       CVE-2007-1306, CVE-2007-1561, CVE-2007-1594
                                CVE-2007-1595, CVE-2007-2294, CVE-2007-2297
                                CVE-2007-2488

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             asterisk security update
           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

   The Open Source PBX software Asterisk was updated
   to fix several security related bugs that allowed attackers to remotely
   crash asterisk or cause information leaks:

   - CVE-2007-1306: Asterisk allowed remote attackers to cause a denial
     of service (crash) by sending a Session Initiation Protocol (SIP)
     packet without a URI and SIP-version header, which results in a
     NULL pointer dereference.

   - CVE-2007-1561: The channel driver in Asterisk allowed remote
     attackers to cause a denial of service (crash) via a SIP INVITE
     message with an SDP containing one valid and one invalid IP address.

   - CVE-2007-1594: The handle_response function in chan_sip.c in Asterisk
     allowed remote attackers to cause a denial of service (crash)
     via a SIP Response code 0 in a SIP packet.

   - CVE-2007-1595: The Asterisk Extension Language (AEL) in pbx/pbx_ael.c
     in Asterisk does not properly generate extensions, which allows
     remote attackers to execute arbitrary extensions and have an unknown
     impact by specifying an invalid extension in a certain form.

   - CVE-2007-2294: The Manager Interface in Asterisk allowed
     remote attackers to cause a denial of service (crash) by using MD5
     authentication to authenticate a user that does not have a password
     defined in manager.conf, resulting in a NULL pointer dereference.

   - CVE-2007-2297: The SIP channel driver (chan_sip) in Asterisk did not
     properly parse SIP UDP packets that do not contain a valid response
     code, which allows remote attackers to cause a denial of service
     (crash).

   - CVE-2007-2488: The IAX2 channel driver (chan_iax2) in Asterisk
     did not properly null terminate data, which allows remote attackers     to trigger loss of transmitted data, and possibly obtain sensitive
     information (memory contents) or cause a denial of service
     (application crash), by sending a frame that lacks a 0 byte.

2) Solution or Work-Around

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

3) Special Instructions and Notes

   None.

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:

   openSUSE 10.2:
             00b2cfd6b8ac2d7d433992b0b1443c11

   SUSE LINUX 10.1:
             de8d3bf81cf5ba905383e9d18e416185

   Power PC Platform:

   openSUSE 10.2:
             c8d7b98b1a96e8aa212bc763c2e609ba

   SUSE LINUX 10.1:
             2c7a49f6ccfc6098dfe721069cb6450f

   x86-64 Platform:

   openSUSE 10.2:
             e293c4ca8f494925ede2b379ec5db220

   SUSE LINUX 10.1:
             a54c6f445b9f5fb2bec9f73dd3c2235c

   Sources:

   openSUSE 10.2:
             a27514b489a70f9941eca06afc2f7c99

   SUSE LINUX 10.1:
             205e2ec41fd07acf4cfb91ab152d2d90

______________________________________________________________________________

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:

    opensuse-security@opensuse.org
        -   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
                .

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