-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: opera
Announcement ID: SUSE-SA:2005:031
Date: Wed, 15 Jun 2005 12:00:00 +0000
Affected Products: 8.2, 9.0, 9.1, 9.2, 9.3
Vulnerability Type: phishing problems
Severity (1-10): 5
SUSE Default Package: no
Cross-References: CAN-2005-0235
CAN-2005-0456
CAN-2005-1139
Content of This Advisory:
1) Security Vulnerability Resolved:
various 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 commercial web browser Opera has been updated to the 8.0 version,
fixing all currently known security problems, including:
- CAN-2005-0235: IDN cloaking / homograph attack allows easy
spoofing of domain names.
- CAN-2005-0456: Opera did not validate base64 encoded binary in data:
URLs correctly.
- CAN-2005-1139: Opera showed the Organizational Information of SSL
certificates which could be easily spoofed and be used for phishing
attacks.
A full Changelog can be found on:
https://www.opera.com:443/browsers/opera
2) Solution or Work-Around
Install the upgraded package.
3) Special Instructions and Notes
Please restart 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 file name 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:
a40ceec9a6772cce634f71b29b7662e3
SUSE Linux 9.2:
f98b646f453a74ddba61ed96f91436ca
SUSE Linux 9.1:
26b3ec794d410a602dde7a29faf030a2
source rpm(s):
b47bf4581a2a3c2872c6eb6fb673ccb4
SUSE Linux 9.0:
508aaa40dc941a4ddb72db32157aa085
source rpm(s):
5b5bc67f61bffdf2898dbf8f5115a6e5
SUSE Linux 8.2:
37bfb1ef0c97c37c5e333c24989222af
source rpm(s):
50b835400caba7938160ace7c4a07680
x86-64 Platform:
SUSE Linux 9.3:
7ab3f0794de27b6e8d1ec1195eca6f7e
source rpm(s):
fafb0ebee70a9479e7611074a687650e
SUSE Linux 9.2:
afecc0d9d633d73537057641ec8496ee
source rpm(s):
baa386aa97a05661ab4f3120e8b5b207
SUSE Linux 9.1:
91a52710d7555fd98ebb021e523e6e78
source rpm(s):
c32e1512c575725e9d8b33251649f691
SUSE Linux 9.0:
8f7a5a4c669a552383418ef7a8bd8d19
source rpm(s):
891bd2022d4d487c0008e9f57ab45779
______________________________________________________________________________
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.
====================================================================
