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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                java-1_6_0-ibm
        Announcement ID:        SUSE-SA:2010:004
        Date:                   Tue, 12 Jan 2010 17:00:00 +0000
        Affected Products:      SLE 11
                                SLES 11
        Vulnerability Type:     remote code execution
        CVSS v2 Base Score:     9.3 (AV:N/AC:M/Au:N/C:C/I:C/A:C)
        SUSE Default Package:   yes
        Cross-References:       CVE-2009-0217, CVE-2009-3865, CVE-2009-3866
                                CVE-2009-3867, CVE-2009-3868, CVE-2009-3869
                                CVE-2009-3871, CVE-2009-3872, CVE-2009-3873
                                CVE-2009-3874, CVE-2009-3875, CVE-2009-3876
                                CVE-2009-3877

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             IBM Java 6 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 was updated to Service Refresh 7.

   The following security issues were fixed:
   CVE-2009-3876
   CVE-2009-3877: A vulnerability in the Java Runtime Environment with
   decoding DER encoded data might allow a remote client to cause the
   JRE to crash, resulting in a denial of service condition.

   CVE-2009-3867: A buffer overflow vulnerability in the Java Runtime
   Environment audio system might allow an untrusted applet or Java Web
   Start application to escalate privileges. For example, an untrusted
   applet might grant itself permissions to read and write local files,
   or run local applications that are accessible to the user running
   the untrusted applet.

   CVE-2009-3868: A buffer overflow vulnerability in the Java Runtime
   Environment with parsing image files might allow an untrusted applet
   or Java Web Start application to escalate privileges. For example,
   an untrusted applet might grant itself permissions to read and write
   local files, or run local applications that are accessible to the
   user running the untrusted applet.

   CVE-2009-3872: An integer overflow vulnerability in the Java Runtime
   Environment with reading JPEG files might allow an untrusted applet
   or Java Web Start application to escalate privileges. For example,
   an untrusted applet might grant itself permissions to read and write
   local files, or run local applications that are accessible to the
   user running the untrusted applet.

   CVE-2009-3873: A buffer overflow vulnerability in the Java Runtime
   Environment with processing JPEG files might allow an untrusted applet
   or Java Web Start application to escalate privileges. For example,
   an untrusted applet might grant itself permissions to read and write
   local files, or run local applications that are accessible to the
   user running the untrusted applet.

   CVE-2009-3875: A security vulnerability in the Java Runtime
   Environment with verifying HMAC digests might allow authentication to
   be bypassed. This action can allow a user to forge a digital signature
   that would be accepted as valid.  Applications that validate HMAC-based
   digital signatures might be vulnerable to this type of attack.

   CVE-2009-3865: A command execution vulnerability in the Java Runtime
   Environment Deployment Toolkit might be used to run arbitrary
   code. This issue might occur as the result of a user of the Java
   Runtime Environment viewing a specially crafted web page that exploits
   this vulnerability.

   CVE-2009-3869: A buffer overflow vulnerability in the Java Runtime
   Environment with processing image files might allow an untrusted applet
   or Java Web Start application to escalate privileges. For example,
   an untrusted applet might grant itself permissions to read and write
   local files or run local applications that are accessible to the user
   running the untrusted applet.

   CVE-2009-3871: A buffer overflow vulnerability in the Java Runtime
   Environment with processing image files might allow an untrusted applet
   or Java Web Start application to escalate privileges. For example,
   an untrusted applet might grant itself permissions to read and write
   local files or run local applications that are accessible to the user
   running the untrusted applet.

   CVE-2009-3866: A security vulnerability in the Java Web Start Installer
   might be used to allow an untrusted Java Web Start application to
   run as a trusted application and run arbitrary code. This issue might
   occur as the result of a user of the Java Runtime Environment viewing
   a specially crafted web page that exploits this vulnerability.

   CVE-2009-3874: An integer overflow vulnerability in the Java Runtime
   Environment with processing JPEG images might allow an untrusted applet
   or Java Web Start application to escalate privileges. For example,
   an untrusted applet might grant itself permissions to read and write
   local files or run local applications that are accessible to the user
   running the untrusted applet.

   CVE-2009-0217: A vulnerability with verifying HMAC-based XML digital
   signatures in the XML Digital Signature implementation included with
   the Java Runtime Environment (JRE) might allow authentication to be
   bypassed. Applications that validate HMAC-based XML digital signatures
   might be vulnerable to this type of attack.
   Note: This vulnerability cannot be exploited by an untrusted applet
   or Java Web Start application.

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 IBM Java 6 applications 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.

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

   SLES 11
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=39e43680df27683c7e496d57e45f7060

   SLE 11
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=39e43680df27683c7e496d57e45f7060

______________________________________________________________________________

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