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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                java-1_6_0-ibm
        Announcement ID:        SUSE-SA:2011:006
        Date:                   Tue, 25 Jan 2011 12:00:00 +0000
        Affected Products:      SUSE Linux Enterprise Java 10 SP3
                                SUSE Linux Enterprise Server 10 SP3
                                SUSE Linux Enterprise Software Development Kit 11 SP1
                                SUSE Linux Enterprise Java 11 SP1
                                SUSE Linux Enterprise Server 11 SP1
        Vulnerability Type:     remote code execution
        CVSS v2 Base Score:     10.0 (AV:N/AC:L/Au:N/C:C/I:C/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2009-3555, CVE-2010-0771, CVE-2010-1321
                                CVE-2010-3541, CVE-2010-3548, CVE-2010-3549
                                CVE-2010-3550, CVE-2010-3551, CVE-2010-3553
                                CVE-2010-3555, CVE-2010-3556, CVE-2010-3557
                                CVE-2010-3558, CVE-2010-3559, CVE-2010-3560
                                CVE-2010-3562, CVE-2010-3563, CVE-2010-3565
                                CVE-2010-3566, CVE-2010-3567, CVE-2010-3568
                                CVE-2010-3569, CVE-2010-3571, CVE-2010-3572
                                CVE-2010-3573, CVE-2010-3574

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             IBM Java 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

   IBM Java 6 SR9 was released, fixing lots of security issues.

   Following CVE entries are cross referenced by this update:
   CVE-2010-3553 CVE-2009-3555 CVE-2010-3562 CVE-2010-3557
   CVE-2010-3558 CVE-2010-3563 CVE-2010-0771 CVE-2010-3550
   CVE-2010-3549 CVE-2010-3551 CVE-2010-3555 CVE-2010-3556
   CVE-2010-3559 CVE-2010-3548 CVE-2010-1321 CVE-2010-3565
   CVE-2010-3567 CVE-2010-3566 CVE-2010-3568 CVE-2010-3541
   CVE-2010-3569 CVE-2010-3571 CVE-2010-3572 CVE-2010-3560
   CVE-2010-3573 CVE-2010-3574

   IBM JDK Alerts can also be found on this page:
   https://www.ibm.com/support/pages/java-sdk/

2) Solution or Work-Around

3) Special Instructions and Notes

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   "Online Update" module or the "zypper" commandline tool. The package and
   patch management stack will detect which updates are required and
   automatically perform 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.

   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:

   SUSE Linux Enterprise Server 10 SP3
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Java 10 SP3
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Server 11 SP1
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Java 11 SP1
     https://login.microfocus.com/nidp/app/login

   SUSE Linux Enterprise Software Development Kit 11 SP1
     https://login.microfocus.com/nidp/app/login

______________________________________________________________________________

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.

    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.

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