-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: opera
Announcement ID: SUSE-SA:2005:057
Date: Mon, 26 Sep 2005 15:00:00 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX OSS 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
SuSE Linux 9.0
Vulnerability Type: remote code execution
Severity (1-10): 6
SUSE Default Package: yes
Cross-References: CAN-2005-3006
CAN-2005-3007
Content of This Advisory:
1) Security Vulnerability Resolved:
opera script insertion 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
This update upgrades the Opera web browser to the 8.50 release.
Besides the changes in 8.50 that are listed in
https://help.opera.com/en/latest/
following security problems were fixed:
1. Attached files are opened without any warnings directly from the
user's cache directory. This can be exploited to execute arbitrary
Javascript in context of "file://".
2. Normally, filename extensions are determined by the "Content-Type"
in Opera Mail. However, by appending an additional '.' to the end of
a filename, an HTML file could be spoofed to be e.g. "image.jpg.".
These two vulnerabilities combined may be exploited to conduct script
insertion attacks if the user chooses to view an attachment named
e.g. "image.jpg." e.g. resulting in disclosure of local files.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please restart running instances of Opera 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 9.3:
14d5e5fa885cdcbfe295bf14e78cc597
SUSE LINUX 9.2:
d49cde72a2ca0a577b1f46d642177a2c
SUSE LINUX 9.1:
37d049f6e1c74d93d53c8369e3c7d38a
source rpm(s):
d186e1294cee84c3472df1ac84a3d6a2
SuSE Linux 9.0:
c9e8a2b20726590afafed2acf33878e5
source rpm(s):
ba618d920bd3c67198a6cfe81417f505
SUSE LINUX OSS 10.0:
f6fd16f597c24c44ff22d3079d67bf04
source rpm(s):
f4d1a6f0d53de4d0a3c66342b39a1090
x86-64 Platform:
SUSE LINUX 9.3:
5e7cc77dffeeb6f7f49040fe57a24436
source rpm(s):
51bdcf29e4838f37c513db2fda7ce4cb
SUSE LINUX 9.2:
92ae1f3adca409fc7504f75eb9a048cd
source rpm(s):
0068542ea265d222909b1a7afb2efd5d
SUSE LINUX 9.1:
26e585d3cd1b813a5fc5905d00ea8c41
source rpm(s):
e1d6ab204a6b53257f883e0319001862
SuSE Linux 9.0:
eb553979fd5085a91fa2d31faff03f8f
source rpm(s):
6495e097ae44fb75e9db8407bc2ce793
SUSE LINUX 10.0:
150053c82d63a0e33472eaa656417b32
source rpm(s):
db1da6ab611d0c70f46602585d0868d4
______________________________________________________________________________
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.
====================================================================
