-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: IBMJava2
Announcement ID: SUSE-SA:2007:010
Date: Thu, 18 Jan 2007 14:00:00 +0000
Affected Products: UnitedLinux 1.0
SuSE Linux Enterprise Server 8
SuSE Linux Openexchange Server 4
SuSE Linux Standard Server 8
SuSE Linux School Server
SUSE LINUX Retail Solution 8
SUSE SLES 9
Open Enterprise Server
Novell Linux POS 9
SLE SDK 10
SUSE SLES 10
Vulnerability Type: remote code execution
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2006-4339, CVE-2006-4790, CVE-2006-6731
CVE-2006-6736, CVE-2006-6737, CVE-2006-6745
Content of This Advisory:
1) Security Vulnerability Resolved:
IBMJava 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
Various security problems and bugs have been fixed in the IBMJava
JRE and SDK.
The IBM Java packages were updated to:
- IBM Java 1.4.2 to Service Refresh 7.
- IBM JAVA 1.3.10 to Service Refresh 10.
It contains several security fixes also fixed in SUN Java including:
- CVE-2006-4339: fix for the RSA exponent padding attack.
- CVE-2006-6736,CVE-2006-6737: 2 unspecified vulnerabilities that
allow untrusted applets to access data in other applets.
- CVE-2006-6745: Multiple unspecified vulnerabilities that allow
applets to gain privileges related to serialization bugs in the JRE.
- CVE-2006-6731: Multiple buffer overflows in java image handling
routines that allow attackers to potentially read/write/execute
local files.
A full overview is at:
https://www.ibm.com/us-en
The update also contains important timezone updates:
- US daylight saving time update starting 2007.
- Western Australia daylight savings time introduction in December 2006.
- A general update to current timezone data-set.
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 programs using
IBMJava 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:
UnitedLinux 1.0
http://support.novell.com/techcenter/psdb/95188799cf297558f0fc915c9d248d1a.html
SuSE Linux Openexchange Server 4
http://support.novell.com/techcenter/psdb/95188799cf297558f0fc915c9d248d1a.html
SuSE Linux Enterprise Server 8
http://support.novell.com/techcenter/psdb/95188799cf297558f0fc915c9d248d1a.html
SuSE Linux Standard Server 8
http://support.novell.com/techcenter/psdb/95188799cf297558f0fc915c9d248d1a.html
SuSE Linux School Server
http://support.novell.com/techcenter/psdb/95188799cf297558f0fc915c9d248d1a.html
SUSE LINUX Retail Solution 8
http://support.novell.com/techcenter/psdb/95188799cf297558f0fc915c9d248d1a.html
SUSE SLES 10
http://support.novell.com/techcenter/psdb/8924ac6b994acb949a8ad3572aba51d6.html
SLE SDK 10
http://support.novell.com/techcenter/psdb/8924ac6b994acb949a8ad3572aba51d6.html
Open Enterprise Server
http://support.novell.com/techcenter/psdb/f5b3f5adf5613e923c01c813a0923b58.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/f5b3f5adf5613e923c01c813a0923b58.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/f5b3f5adf5613e923c01c813a0923b58.html
______________________________________________________________________________
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.
There are two verification methods that can be used independently from
each other to prove the authenticity of a downloaded file or RPM package:
1) Using the internal gpg signatures of the rpm package
2) MD5 checksums as provided in this announcement
1) 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.
2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. Execute the command
md5sum
after you downloaded the file from a SUSE FTP server or its mirrors.
Then compare the resulting md5sum with the one that is listed in the
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.
- 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
.
suse-security-announce@suse.com
- 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.
====================================================================
