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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                acroread, acroread_ja
        Announcement ID:        SUSE-SA:2009:049
        Date:                   Mon, 26 Oct 2009 12:00:00 +0000
        Affected Products:      openSUSE 10.3
                                openSUSE 11.0
                                openSUSE 11.1
                                SUSE Linux Enterprise Desktop 10 SP2
                                SUSE Linux Enterprise Desktop 10 SP3
                                SLED 11
        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2007-0045, CVE-2007-0048, CVE-2009-2564
                                CVE-2009-2979, CVE-2009-2980, CVE-2009-2981
                                CVE-2009-2982, CVE-2009-2983, CVE-2009-2985
                                CVE-2009-2986, CVE-2009-2988, CVE-2009-2990
                                CVE-2009-2991, CVE-2009-2992, CVE-2009-2993
                                CVE-2009-2994, CVE-2009-2996, CVE-2009-2997
                                CVE-2009-2998, CVE-2009-3431, CVE-2009-3458
                                CVE-2009-3459, CVE-2009-3462

    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:
            - see SUSE Security Summary Report
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   Adobe Reader has been updated to fix numerous security
   vulnerabilities. Some of the vulnerabilities allowed attackers to
   potentially execute arbitrary code on the victim's system via
   specially crafted PDF files.

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.1:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/i586/acroread-8.1.7-0.1.1.i586.rpm
   
   openSUSE 11.0:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/rpm/i586/acroread-8.1.7-0.1.i586.rpm
   
   openSUSE 10.3:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/10.3/rpm/i586/acroread-8.1.7-0.1.i586.rpm
   
   Sources:
   
   openSUSE 11.1:
      
   openSUSE 11.0:
      
   openSUSE 10.3:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/10.3/rpm/src/acroread-8.1.7-0.1.nosrc.rpm
   
   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:
   
   SUSE Linux Enterprise Desktop 10 SP3
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=c7ba3c517224717a03bcb3b56d7b3550
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=538748b7a9bae219da3187e837f552ac
   
   SUSE Linux Enterprise Desktop 10 SP2
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=22acf3dce2d8d08b8c86942030ba5d0f
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=827a9624665ce152f7b0e6972059796a
   
   SLED 11
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=ce38af327adaced851154dd69b821772
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=da542e714548e7606e770f4fa3ce65f8
   
   SLES 11 DEBUGINFO
     https://login.microfocus.com/nidp/app/login;set_restricted=true&keywords=da542e714548e7606e770f4fa3ce65f8

______________________________________________________________________________

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.

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