SUSE Security Announcement: flash player (SUSE-SA:2010:024)

______________________________________________________________________________

SUSE Security Announcement

Package: flash-player
Announcement ID: SUSE-SA:2010:024
Date: Fri, 11 Jun 2010 17:00:00 +0000
Affected Products: openSUSE 11.0
openSUSE 11.1
openSUSE 11.2
SUSE Linux Enterprise Desktop 10 SP3
SUSE Linux Enterprise Desktop 11
SUSE Linux Enterprise Desktop 11 SP1
Vulnerability Type: remote code execution
CVSS v2 Base Score: 9.3 (AV:N/AC:M/Au:N/C:C/I:C/A:C)
SUSE Default Package: yes
Cross-References: CVE-2008-4546, CVE-2009-3793, CVE-2010-1297
CVE-2010-2160, CVE-2010-2161, CVE-2010-2162
CVE-2010-2163, CVE-2010-2164, CVE-2010-2165
CVE-2010-2166, CVE-2010-2167, CVE-2010-2169
CVE-2010-2170, CVE-2010-2171, CVE-2010-2172
CVE-2010-2173, CVE-2010-2174, CVE-2010-2175
CVE-2010-2176, CVE-2010-2177, CVE-2010-2178
CVE-2010-2179, CVE-2010-2180, CVE-2010-2181
CVE-2010-2182, CVE-2010-2183, CVE-2010-2184
CVE-2010-2185, CVE-2010-2186, CVE-2010-2187
CVE-2010-2188, CVE-2010-2189

Content of This Advisory:
1) Security Vulnerability Resolved:
flash-player 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

Adobe Flash Player was updated to fix multiple critical security
vulnerabilities which allow an attacker to remotely execute arbitrary
code or to cause a denial of service.

The Flash Plugin was upgraded to version 10.1.53.64.

The following CVE numbers have been assigned:
CVE-2008-4546, CVE-2009-3793, CVE-2010-1297, CVE-2010-2160,
CVE-2010-2161, CVE-2010-2162, CVE-2010-2163, CVE-2010-2164,
CVE-2010-2165, CVE-2010-2166, CVE-2010-2167, CVE-2010-2169,
CVE-2010-2170, CVE-2010-2171, CVE-2010-2172, CVE-2010-2173,
CVE-2010-2174, CVE-2010-2175, CVE-2010-2176, CVE-2010-2177,
CVE-2010-2178, CVE-2010-2179, CVE-2010-2180, CVE-2010-2181,
CVE-2010-2182, CVE-2010-2183, CVE-2010-2184, CVE-2010-2185,
CVE-2010-2186, CVE-2010-2187, CVE-2010-2188, CVE-2010-2189

The standalone flash player was not yet updated by Adobe and will be
fixed in a future update.

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 your Webbrowser 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:

openSUSE 11.2:
http://download.opensuse.org/update/11.2/rpm/i586/flash-player-10.1.53.64-1.1.1.i586.rpm

openSUSE 11.1:
http://download.opensuse.org/update/11.1/rpm/i586/flash-player-10.1.53.64-1.1.1.i586.rpm

openSUSE 11.0:
http://download.opensuse.org/update/11.0/rpm/i586/flash-player-10.1.53.64-1.1.i586.rpm

Sources:

openSUSE 11.2:
http://download.opensuse.org/update/11.2/rpm/src/flash-player-10.1.53.64-1.1.1.src.rpm

openSUSE 11.1:
http://download.opensuse.org/update/11.1/rpm/src/flash-player-10.1.53.64-1.1.1.src.rpm

openSUSE 11.0:
http://download.opensuse.org/update/11.0/rpm/src/flash-player-10.1.53.64-1.1.src.rpm

Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:

SUSE Linux Enterprise Desktop 10 SP3
http://download.novell.com/patch/finder/?keywords=95c1970351eaad8ec7445af7b6974ebe

SUSE Linux Enterprise Desktop 11 SP1
http://download.novell.com/patch/finder/?keywords=9fed1ac7d6ac263f8b42cb8e24927e67

SUSE Linux Enterprise Desktop 11
http://download.novell.com/patch/finder/?keywords=dc5e2e29ebe98d9444b78ef5643bf4f1

______________________________________________________________________________

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.

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.