The IBM Java JRE 5 was brought to Service Release 9 fixing quite a number of security issues and bugs. The update fixes the following security problems...
______________________________________________________________________________
SUSE Security Announcement
Package: IBMJava5-JRE,java-1_5_0-ibm
Announcement ID: SUSE-SA:2009:007
Date: Thu, 29 Jan 2009 14:00:00 +0000
Affected Products: SUSE SLES 9
Open Enterprise Server
Novell Linux POS 9
SUSE Linux Enterprise Desktop 10 SP2
SUSE Linux Enterprise Server 10 SP2
Vulnerability Type: local privilege escalation
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2008-2086, CVE-2008-5339, CVE-2008-5340
CVE-2008-5341, CVE-2008-5342, CVE-2008-5343
CVE-2008-5344, CVE-2008-5345, CVE-2008-5346
CVE-2008-5348, CVE-2008-5350, CVE-2008-5351
CVE-2008-5352, CVE-2008-5353, CVE-2008-5354
CVE-2008-5356, CVE-2008-5357, CVE-2008-5359
CVE-2008-5360
Content of This Advisory:
1) Security Vulnerability Resolved:
IBM Java security problems
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
The IBM Java JRE 5 was brought to Service Release 9 fixing quite a
number of security issues and bugs.
The update fixes the following security problems:
CVE-2008-5350: A security vulnerability in the Java Runtime Environment
(JRE) may allow an untrusted applet or application to list the contents
of the home directory of the user running the applet or application.
CVE-2008-5346: A security vulnerability in the Java Runtime Environment
(JRE) with parsing zip files may allow an untrusted applet or
application to read arbitrary memory locations in the process that
the applet or application is running in.
CVE-2008-5343: A vulnerability in Java Web Start and Java Plug-in may
allow hidden code on a host to make network connections to that host
and to hijack HTTP sessions using cookies stored in the browser.
CVE-2008-5344: A vulnerability in the Java Runtime Environment
(JRE) with applet classloading may allow an untrusted applet to read
arbitrary files on a system that the applet runs on and make network
connections to hosts other than the host it was loaded from.
CVE-2008-5359: A buffer overflow vulnerability in the Java Runtime
Environment (JRE) image processing code 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-2008-5341: A vulnerability in the Java Runtime Environment
may allow an untrusted Java Web Start application to determine the
location of the Java Web Start cache and the user name of the user
running the Java Web Start application.
CVE-2008-5339: A vulnerability in the Java Runtime Environment (JRE)
may allow an untrusted Java Web Start application to make network
connections to hosts other than the host that the application is
downloaded from.
CVE-2008-5340: A vulnerability in the Java Runtime Environment with
launching Java Web Start applications 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-2008-5348: A security vulnerability in the Java Runtime Environment
(JRE) with authenticating users through Kerberos may lead to a Denial
of Service (DoS) to the system as a whole, due to excessive consumption
of operating system resources.
CVE-2008-2086: A vulnerability in Java Web Start may allow certain
trusted operations to be performed, such as modifying system
properties.
CVE-2008-5345: The Java Runtime Environment (JRE) allows code loaded
from the local filesystem to access localhost. This may allow code that
is maliciously placed on the local filesystem and then subsequently
run, to have network access to localhost that would not otherwise
be allowed if the code were loaded from a remote host. This may be
leveraged to steal cookies and hijack sessions (for domains that map
a name to the localhost).
CVE-2008-5351: The UTF-8 (Unicode Transformation Format-8) decoder in
the Java Runtime Environment (JRE) accepts encodings that are longer
than the "shortest" form. This behavior is not a vulnerability in Java
SE. However, it may be leveraged to exploit systems running software
that relies on the JRE UTF-8 decoder to reject non-shortest form
sequences. For example, non-shortest form sequences may be decoded
into illegal URIs, which may then allow files that are not otherwise
accessible to be read, if the URIs are not checked following UTF-8
decoding.
CVE-2008-5360: The Java Runtime Environment creates temporary files
with insufficiently random names. This may be leveraged to write JAR
files which may then be loaded as untrusted applets and Java Web Start
applications to access and provide services from localhost and hence
steal cookies.
CVE-2008-5353: A security vulnerability in the Java Runtime Environment
(JRE) related to deserializing calendar objects 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-2008-5356: A buffer vulnerability in the Java Runtime Environment
(JRE) 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-2008-5354: A buffer overflow vulnerability in the Java Runtime
Environment (JRE) may allow an untrusted Java application that is
launched through the command line to escalate privileges. For example,
the untrusted Java application may grant itself permissions to read
and write local files or execute local applications that are accessible
to the user running the untrusted Java application.
This vulnerability cannot be exploited by an applet or Java Web
Start application.
CVE-2008-5357: A buffer vulnerability in the Java Runtime Environment
(JRE) 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-2008-5352: A buffer overflow vulnerability 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-2008-5342: A security vulnerability in the the Java Web Start
BasicService allows untrusted applications that are downloaded from
another system to request local files to be displayed by the browser
of the user running the untrusted application.
References can be found on:
http://www-128.ibm.com/developerworks/java/jdk/alerts/
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Make sure you restart all Java using applications after installing this update.
While letting them run will usually work, they for instance lose access to dynamically
loaded information like timezone data.
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:
SUSE Linux Enterprise Server 10 SP2
http://download.novell.com/index.jsp?search=Search&keywords=9a91147409995ade2d60bff341961c31
SUSE Linux Enterprise Desktop 10 SP2
http://download.novell.com/index.jsp?search=Search&keywords=9a91147409995ade2d60bff341961c31
Open Enterprise Server
http://download.novell.com/index.jsp?search=Search&keywords=8671eb8081c281a0c30b3955c9f0a7b6
Novell Linux POS 9
http://download.novell.com/index.jsp?search=Search&keywords=8671eb8081c281a0c30b3955c9f0a7b6
SUSE SLES 9
http://download.novell.com/index.jsp?search=Search&keywords=8671eb8081c281a0c30b3955c9f0a7b6
______________________________________________________________________________
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.
=====================================================================
______________________________________________________________________________
The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular, the
clear text signature should show proof of the authenticity of the text.
SUSE Linux Products GmbH provides no warranties of any kind whatsoever
with respect to the information contained in this security advisory.
The IBM Java JRE 5 was brought to Service Release 9 fixing quite a number of security issues and bugs. The update fixes the following security problems...