SUSE Security Announcement: Acrobat Reader (SUSE-SA:2010:029)

______________________________________________________________________________

SUSE Security Announcement

Package: acroread
Announcement ID: SUSE-SA:2010:029
Date: Thu, 08 Jul 2010 11: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-2010-1240, CVE-2010-1285, CVE-2010-1295
CVE-2010-1297, CVE-2010-2168, CVE-2010-2201
CVE-2010-2202, CVE-2010-2203, CVE-2010-2204
CVE-2010-2205, CVE-2010-2206, CVE-2010-2207
CVE-2010-2208, CVE-2010-2209, CVE-2010-2210
CVE-2010-2211, CVE-2010-2212, APSB10-15

Content of This Advisory:
1) Security Vulnerability Resolved:
Acrobat Reader 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:
Summary Report.
6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

Acrobat Reader was updated to version 9.3.3 to fix lots of security
issues and bugs, several of whom could be used to execute code by
trick the target user to open specially crafted PDFs.

Adobes advisory can be found here:
Adobe - Security Bulletins: APSB10-15 - Security updates available for Adobe Reader and Acrobat

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 Acrobat Reader 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:
302 Found

openSUSE 11.1:
302 Found

openSUSE 11.0:
302 Found

Platform Independent:

openSUSE 11.2:
302 Found
302 Found
302 Found
302 Found
302 Found

openSUSE 11.1:
302 Found
302 Found
302 Found
302 Found
302 Found

openSUSE 11.0:
302 Found
302 Found
302 Found
302 Found
302 Found

Sources:

openSUSE 11.2:
302 Found
302 Found

openSUSE 11.1:
302 Found
302 Found

openSUSE 11.0:
302 Found
302 Found

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

SUSE Linux Enterprise Desktop 10 SP3
NOVELL: Patch Finder
NOVELL: Patch Finder

SUSE Linux Enterprise Desktop 11 SP1
NOVELL: Patch Finder
NOVELL: Patch Finder

SUSE Linux Enterprise Desktop 11
NOVELL: Patch Finder
NOVELL: Patch Finder

______________________________________________________________________________

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.