-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: opera
Announcement ID: SUSE-SA:2005:034
Date: Wed, 22 Jun 2005 16:00:00 +0000
Affected Products: 8.2, 9.0, 9.1, 9.2, 9.3
Vulnerability Type: remote code execution
Severity (1-10): 7
SUSE Default Package: no
Cross-References: CAN-2005-1475
CAN-2005-1669
CAN-2004-1157
Content of This Advisory:
1) Security Vulnerability Resolved:
various security problems in Opera
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 web browser Opera has been updated to version 8.01 to fix various
security-related bugs.
* Fixed XMLHttpRequest redirect vulnerability reported in Secunia
Advisory 15008.
* Fixed cross-site scripting vulnerability reported in Secunia
Advisory 15411.
* Fixed cross-site scripting vulnerability in location header when
automatic redirection is disabled. Vulnerability reported in Secunia
Advisory 15423.
* Fix for variant of window injection vulnerability reported in Secunia
Advisory 13253
* Fixed information disclosure weakness causing file path information
to be sent when using the GET form method. Security Focus Bugtraq
ID #12723.
* Improved accuracy of security bar and modified security icon
behavior: when a certificate is accepted manually after a warning,
the security level of the connection is set to 1.
* Fixed issue with wrong referrers being sent to sites in browsing
history.
* Fixed erroneous display of certificate names containing ampersands.
* Solved problem with collapsed address bars for some pop-ups
missing indication of security level.
These issues are tracked by the Mitre CVE IDs CAN-2005-1475,
CAN-2005-1669 and CAN-2004-1157.
2) Solution or Work-Around
Please install the upgraded package.
3) Special Instructions and Notes
None.
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.
x86 Platform:
SUSE Linux 9.3:
b735a0e3e238cded7db42018d371dc10
SUSE Linux 9.2:
f6a6c2d1562db07c21f69176b3b873c3
SUSE Linux 9.1:
3f4bdc3f1fa6a4895b099e1b517acb0f
source rpm(s):
853832a3070d6fdd4b55337381e54ab5
SUSE Linux 9.0:
2ab574cae977d4594c90f7f24fe3a35e
source rpm(s):
1f9e06245625f1b7bac0359ef5e42617
SUSE Linux 8.2:
64321e073068dba4a08ad655671bb0de
source rpm(s):
ce9c2795a066856899de3a3cd3f5ae3f
x86-64 Platform:
SUSE Linux 9.3:
1748a5fa7a49dcaee5e46e7eca799bc3
source rpm(s):
2f6ea5cb149704ad0ea7248a5fa41b6f
SUSE Linux 9.2:
b8e11857750ee82fe0b2b96c548e88bd
source rpm(s):
6b20c173d980ce5c2c10c83cf722ff8e
SUSE Linux 9.1:
94f5e8bf7ab08d3c79f391a14648afa2
source rpm(s):
38c284a3241c2e4a25d56f65c20df16e
SUSE Linux 9.0:
4f04f1df035b03857915dbad665d9477
source rpm(s):
4d318c94bd2ba7ee3ac258d8803153af
______________________________________________________________________________
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.
====================================================================
