-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: kdelibs3
Announcement ID: SUSE-SA:2006:003
Date: Fri, 20 Jan 2006 15:00:00 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
SUSE SLES 9
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2006-0019
Content of This Advisory:
1) Security Vulnerability Resolved:
buffer overflow in kjs JavaScript interpreter
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
Maksim Orlovich discovered a bug in the JavaScript interpreter used
by Konqueror. UTF-8 encoded URLs could lead to a buffer overflow
that causes the browser to crash or execute arbitrary code.
Attackers could trick users into visiting specially crafted web
sites that exploit this bug (CVE-2006-0019).
2) Solution or Work-Around
JavaScript can be disabled in Konqueror's settings dialog to prevent
exploitation. Some websites may no longer work with disabled
JavaScript though. It is recommended to install the update packages.
3) Special Instructions and Notes
Please close and restart KDE 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.
x86 Platform:
SUSE LINUX 10.0:
4da8595fe0d3c701e806032625d67062
f65fe6cc710958987d7f1091e495e78d
SUSE LINUX 9.3:
c39e37cec38e079d5b1151c6adeb8d43
45143c3f3f9255e11b6f6847d1cf4cde
SUSE LINUX 9.2:
c391743607a2172222a507ef14d932cd
277ac4cbb60108065e238ba69687c30e
SUSE LINUX 9.1:
6ea9bf914237736465798eb49159f505
468d28e2f0197338547ebc47043dbfaa
518250500bc4273fd9a1dfa58dd50fb9
Power PC Platform:
SUSE LINUX 10.0:
645ce5753fcaced95e7045e4ba2baa73
803b30418ecad1605c01c0acaa762f90
x86-64 Platform:
SUSE LINUX 10.0:
08d09df2cfbac860b8f45981bd1a8579
5bb97f9539926bb53e02940b5e20ec31
e69607737e2bcdcecc8022e9bbda9182
SUSE LINUX 9.3:
da3a139ef5d48d2d74a4d7765cd2c9ef
3aa26c0f85df70264adb2f2728efe354
7759332a6d673e473396caf58fc37809
SUSE LINUX 9.2:
09c2ac4f36551962cc6913d91d9d5cc8
f1ff64a1e623352959f4fcdd70063224
807cb8a5e80bd370e0da572a30c7afb8
SUSE LINUX 9.1:
23bfa7a97403484f3ebe61fd052ec3af
58e71b33071f76606ebfba5e47787631
Sources:
SUSE LINUX 10.0:
8ffd6e0aa985efac9b20ee7b6b2f17d3
SUSE LINUX 9.3:
caae379e491c53dd3d9bfd0076fed8e7
SUSE LINUX 9.2:
9c92bfa995b6eb4ac817c1245b45394c
SUSE LINUX 9.1:
d9ace2e104ffd4683c340fc8f145e1d1
85ff708f506a4820e6d2b3b4e3d239fc
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
https://www.suse.com:443/
______________________________________________________________________________
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:
suse-security@suse.com
- 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
.
For general information or the frequently asked questions (FAQ),
send mail to or
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
