SUSE 2006-041 Moderate: Adobe Reader Remote Code Execution Notification

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                acroread
        Announcement ID:        SUSE-SA:2006:041
        Date:                   Tue, 04 Jul 2006 14:00:00 +0000
        Affected Products:      SUSE LINUX 10.1
                                SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE LINUX 9.2
                                SUSE SLES 9
        Vulnerability Type:     unknown
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-3093

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             Acroread security upgrade to 7.0.8
           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

   Various unspecified security problems have been fixed in Acrobat
   Reader version 7.0.8.

   Adobe does not provide detailed information about the nature of the
   security problems. Therefore, it is necessary to assume that remote
   code execution is possible.


   Adobe does not provide update packages for Acroread that are compatible
   with some of our releases from the past. Therefore, updates are missing
   (and might not be provided) for the products listed as follows.

   As a solution to Adobe acroread security problems on older products
   we suggest removal of the package from exposed systems and to use
   the longer maintained open source PDF viewers.

   - SUSE Linux Enterprise Server 9, Open Enterprise Server,
     Novell Linux POS 9

     Acrobat Reader 7.0.8 has a new requirement on GTK+ 2.4 libraries
     (previously GTK+ 2.2).

     Since the above products contain only GTK+ 2.2, the Acrobat Reader
     7.0.8 provided by Adobe is currently not functional.

     We have postponed the updates and wait for Adobe to clarify this
     problem.

   - SUSE Linux Enterprise Server 8, SUSE Linux Enterprise Desktop 1

     These versions only support Acrobat Reader 5 and could not be
     upgraded for Acrobat Reader 7 due to glibc and GTK+ requirements.

     We discontinued security support for Acrobat Reader on those
     products some time ago already.

   This issue is tracked by the Mitre CVE ID CVE-2006-3093.

2) Solution or Work-Around

   Please install the update packages.

   You can also use the open source PDF viewer replacements, as for
   instance xpdf, kpdf, evince, gpdf or similar programs.

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:

   SUSE LINUX 10.1:
             0a439b3541fec2329b55f3b9b3bc4858

   SUSE LINUX 10.0:
             76d13f4fd89e25549a363ae443cbab04

   SUSE LINUX 9.3:
             953a36fb273d1245a122ea9a0774fcc2

   SUSE LINUX 9.2:
             4691f003b517f23bad4b923f24f45133

   Sources:

   SUSE LINUX 10.1:
             cdf32850c4a770fe4458df7e78fd0dbe

   SUSE LINUX 10.0:
             76eb5e155e370109b0d55226e8b94895

   SUSE LINUX 9.3:
             e55b674570116b348ba7091f2b8b906e

   SUSE LINUX 9.2:
             97fdaba08621d339fdfde9b94db62a70

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

   SUSE SLES 9
     
______________________________________________________________________________

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.
    ====================================================================