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

______________________________________________________________________________

                        SUSE Security Summary Report

        Announcement ID:        SUSE-SR:2010:002
        Date:                   Mon, 01 Feb 2010 16:00:00 +0000
        Cross-References:       CVE-2009-0758, CVE-2009-3940, CVE-2009-4012
                                CVE-2009-4144, CVE-2009-4145, CVE-2009-4411

    Content of this advisory:
        1) Solved Security Vulnerabilities:
            - virtualbox-ose
            - NetworkManager-gnome
            - avahi
            - acl
            - libthai
        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.

   - virtualbox-ose
     This update of virtualbox-ose fixes a memory consumption bug in the
     kernel code that can be used to allocate almost all physical memory 
     (CVE-2009-3940).
     Affected Products: openSUSE 11.0, 11.1, 11.2

   - NetworkManager-gnome
     nm-applet connected to WPA2 Enterprise networks even if the specified CA
     certificate file didn't exist (CVE-2009-4144).
     
     When editing connections in nm-applet the connection object was exported via
     DBus disclosing potentially sensitive information to local users     (CVE-2009-4145).

     Affected Products: SLE11, openSUSE 11.0, 11.1, 11.2

   - avahi
     The avahi-daemon reflector could cause packet storms when reflecting
     legacy unicast mDNS traffic (CVE-2009-0758).

     Affected Products: SLE10-SP2, SLE10-SP3, SLE11, openSUSE 11.0, 11.1

   - acl
     the getfacl tool followed symbolic links in recursive (-R) mode even
     if the --physical (-P) option was specified (CVE-2009-4411).

     Affected Products: SLE11, openSUSE 11.0, 11.1

   - libthai
     very long strings could lead to a heap buffer overflow in libthai
     (CVE-2009-4012).

     Affected Products: 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.
    ====================================================================