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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                java-1_6_0-ibm
        Announcement ID:        SUSE-SA:2009:036
        Date:                   Thu, 02 Jul 2009 12:00:00 +0000
        Affected Products:      SLE 11
                                SLES 11
        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2009-1093, CVE-2009-1094, CVE-2009-1095
                                CVE-2009-1096, CVE-2009-1097, CVE-2009-1098
                                CVE-2009-1099, CVE-2009-1100, CVE-2009-1101
                                CVE-2009-1103, CVE-2009-1104, CVE-2009-1105
                                CVE-2009-1106, CVE-2009-1107

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             IBM Java 6 SR5 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 SR 5 was released fixing various bugs and critical security
   issues:

   CVE-2009-1093: A vulnerability in the Java Runtime Environment (JRE)
   with initializing LDAP connections may be exploited by a remote client
   to cause a denial-of-service condition on the LDAP service.

   CVE-2009-1094: A vulnerability in Java Runtime Environment LDAP
   client implementation may allow malicious data from an LDAP server
   to cause malicious code to be unexpectedly loaded and executed on an
   LDAP client.

   CVE-2009-1095
   CVE-2009-1096: Buffer overflow vulnerabilities in the Java
   Runtime Environment (JRE) with unpacking applets and Java Web Start
   applications using the unpack200 JAR unpacking utility may allow an
   untrusted applet or application to escalate privileges. For example,
   an untrusted applet may grant itself permissions to read and write
   local files or execute local applications that are accessible to the
   user running the untrusted applet.

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

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

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

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

   CVE-2009-1100: A vulnerability in the Java Runtime Environment (JRE)
   with storing temporary font files may allow an untrusted applet
   or application to consume a disproportionate amount of disk space
   resulting in a denial-of-service condition.

   CVE-2009-1100: A vulnerability in the Java Runtime Environment (JRE)
   with processing temporary font files may allow an untrusted applet or
   application to retain temporary files resulting in a denial-of-service
   condition.

   CVE-2009-1101: A vulnerability in the Java Runtime Environment (JRE)
   HTTP server implementation may allow a remote client to create a
   denial-of-service condition on a JAX-WS service endpoint that runs
   on the JRE.

   CVE-2009-1103: A vulnerability in the Java Plug-in with deserializing
   applets may allow an untrusted applet to escalate privileges. For
   example, an untrusted applet may grant itself permissions to read and
   write local files or execute local applications that are accessible
   to the user running the untrusted applet.

   CVE-2009-1104: The Java Plug-in allows Javascript code that is loaded
   from the localhost to connect to any port on the system. This may
   be leveraged together with XSS vulnerabilities in a blended attack
   to access other applications listening on ports other than the one
   where the Javascript code was served from.

   CVE-2009-1105: The Java Plug-in allows a trusted applet to be launched
   on an earlier version of the Java Runtime Environment (JRE) provided
   the user that downloaded the applet allows it to run on the requested
   release. A vulnerability allows Javascript code that is present in
   the same web page as the applet to exploit known vulnerabilities of
   the requested JRE.

   CVE-2009-1106: A vulnerability in the Java Runtime Environment with
   parsing crossdomain.xml files may allow an untrusted applet to connect
   to any site that provides a crossdomain.xml file instead of sites
   that allow the domain that the applet is running on.

   CVE-2009-1107: The Java Plugin displays a warning dialog for signed
   applets. A signed applet can obscure the contents of the dialog and
   trick a user into trusting the applet.

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 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://download.novell.com/index.jsp?search=Search&set_restricted=true&keywords=706f811c965148739c35d07d3653b91c

   SLE 11
     https://download.novell.com/index.jsp?search=Search&set_restricted=true&keywords=706f811c965148739c35d07d3653b91c

______________________________________________________________________________

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