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

______________________________________________________________________________

                        SUSE Security Summary Report

        Announcement ID:        SUSE-SR:2010:009
        Date:                   Wed, 14 Apr 2010 13:00:00 +0000
        Cross-References:       CVE-2009-1570, CVE-2009-3909, CVE-2010-0132
                                CVE-2010-0421, CVE-2010-0436, CVE-2010-0629

    Content of this advisory:
        1) Solved Security Vulnerabilities:
            - viewvc
            - krb5
            - pango
            - gimp
            - kdebase3, kde4-kdm
        2) Pending Vulnerabilities, Solutions, and Work-Arounds:
            none
        3) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Solved Security Vulnerabilities

   To avoid flooding mailing lists with SUSE Security Announcements for minor
   issues, SUSE Security releases weekly summary reports for the low profile
   vulnerability fixes. The SUSE Security Summary Reports do not list or
   download URLs like the SUSE Security Announcements that are released for
   more severe vulnerabilities.

   Fixed packages for the following incidents are already available on our FTP
   server and via the YaST Online Update.

   - viewvc
     CVS support got broken by the previous viewvc update for
     CVE-2010-0132. This release fixes that again.
     
     Affected Products: openSUSE 11.0, 11.1

   - krb5
     Authenticated users could crash the kadmind process by referencing
     freed memory (CVE-2010-0629).
     
     Affected Products: SLE11, openSUSE 11.0, 11.1

   - pango
     This update of pango fixes a memory corruption bug that could
     potentially be exploited to execute arbitrary code when processing
     fonts from untrusted sources (CVE-2010-0421).
     
     Affected Products: SLE10-SP2, SLE10-SP3
     

   - gimp
     Integer overflows in the BMP and PSD plug-ins potentially allowed attackers to
     execute arbitrary code on the victim's system by tricking the victim to open
     specially crafted files (CVE-2009-1570, CVE-2009-3909).
     
     Affected Products: SLE10-SP2, SLE10-SP3, SLE11, openSUSE 11.0, 11.1, 11.2

   - kdebase3, kde4-kdm
     A race condition in KDM allowed local attackers to trick KDM into
     changing permissions of arbitrary files to be readable by anyone
     (CVE-2010-0436).
     
     Affected Products: SLE10-SP2, SLE10-SP3, SLE11, openSUSE 11.0, 11.1, 11.2


______________________________________________________________________________

2) Pending Vulnerabilities, Solutions, and Work-Arounds

   none
______________________________________________________________________________

3) 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 containing 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 integrity of a
    package needs to be verified to ensure that it has not been tampered with.

    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 included at the end of this
    announcement.

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

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