-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: acroread
Announcement ID: SUSE-SA:2010:008
Date: Tue, 26 Jan 2010 15:00:00 +0000
Affected Products: openSUSE 11.0
openSUSE 11.1
openSUSE 11.2
SLE10-SP2
SLE10-SP3
SLED 11
Vulnerability Type: remote code execution
CVSS v2 Base Score: 6.8 (AV:N/AC:M/Au:N/C:P/I:P/A:P)
SUSE Default Package: yes (on SLED)
Cross-References: CVE-2009-3953, CVE-2009-3954, CVE-2009-3955,
CVE-2009-3956, CVE-2009-3957, CVE-2009-3958,
CVE-2009-3959, CVE-2009-4324
Content of This Advisory:
1) Security Vulnerability Resolved:
Adobe 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:
- transmission
- libopenssl-devel
- gzip
- bind
- viewvc
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
Specially crafted PDF files could crash acroread. Attackers could
potentially exploit that to execute arbitrary code (CVE-2009-3953,
CVE-2009-3954, CVE-2009-3955, CVE-2009-3956, CVE-2009-3957,
CVE-2009-3958, CVE-2009-3959, CVE-2009-4324).
Acrobat reader was updated to version 9.3 to fix the security issues.
Note: Due to integration issues with the major version update of
acroread on SLE10 updates for SLE10 are not ready yet. Fixed
packages will be submitted ASAP.
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 acroread 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://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/acroread-9.3-0.1.1.i586.rpm
openSUSE 11.1:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/i586/acroread-9.3-0.1.1.i586.rpm
openSUSE 11.0:
http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/rpm/i586/acroread-9.3-0.1.i586.rpm
Sources:
openSUSE 11.2:
openSUSE 11.1:
openSUSE 11.0:
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SLED 11
https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=92cc3368337b3767a6a4451406360608
SLES 11 DEBUGINFO
https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=92cc3368337b3767a6a4451406360608
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
- transmission
Specially crafted torrent files could overwrite arbitrary files
(CVE-2010-0012).
Affected Products: openSUSE 11.0, 11.1, 11.2
- libopenssl-devel
Incorrect use of an openssl cleanup function can lead to memory
leaks in applications. For example an ssl enabled web server such as
apache that uses php, curl and openssl leaks memory if a SIGHUP
signal was sent to apache. The openssl cleanup function was made
more robust to avoid memory leaks (CVE-2009-4355).
Affected Products: SLE10-SP2, SLE10-SP3, SLE11, openSUSE 11.0, 11.1, 11.2
- gzip
Specially crafted gzip archives could lead to gzip allocating a too
small huffman table. Attackers could exploit that to crash gzip
(CVE-2009-2624).
Specially crafted gzip archives could trigger integer overflows.
Attackers could exploit that to crash gzip or potentially execute
arbitrary code (CVE-2010-0001). Only 64bit architectures are
affected by this flaw.
Affected Products: SLES9, SLE10-SP2, SLE10-SP3, SLE11, openSUSE 11.0, 11.1, 11.2
- bind
bind when configured for DNSSEC could incorrectly cache NXDOMAIN
responses (CVE-2010-0097). Moreover, the fix for CVE-2009-4022 was
incomplete. Despite the previous fix CNAME and DNAME responses could
be incorrectly cached (CVE-2010-0290).
Affected Products: SLE11, openSUSE 11.0, 11.1, 11.2
- viewvc
viewvc was updated to version 1.1.3 which fixes the following security problems:
- add root listing support of per-root authz config (CVE-2010-0004).
- query.py requires 'forbidden' authorizer (or none) in config (CVE-2010-0005).
Affected Products: openSUSE 11.2
______________________________________________________________________________
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.
- SUSE runs two security mailing lists to which any interested party may
subscribe:
opensuse-security@opensuse.org
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail to
.
opensuse-security-announce@opensuse.org
- SUSE's announce-only mailing list.
Only SUSE's security announcements are sent to this list.
To subscribe, send an e-mail to
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
