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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                acroread
        Announcement ID:        SUSE-SA:2007:011
        Date:                   Mon, 22 Jan 2007 18:00:00 +0000
        Affected Products:      SUSE LINUX 9.3
                                SUSE LINUX 10.0
                                SUSE LINUX 10.1
                                openSUSE 10.2
                                Novell Linux Desktop 9
                                SUSE SLED 10
        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-5857, CVE-2007-0044, CVE-2007-0045
                                CVE-2007-0046, CVE-2007-0047, CVE-2007-0048

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

   The Adobe Acrobat Reader has been updated to version 7.0.9.

   This update also includes following security fixes:

   CVE-2006-5857: A memory corruption problem was fixed in Adobe Acrobat
                  Reader can potentially lead to code execution.

   CVE-2007-0044: Universal Cross Site Request Forgery (CSRF) problems
		  were fixed in the Acrobat Reader plugin which could be
		  exploited by remote attackers to conduct CSRF attacks
		  using any site that is providing PDFs.

   CVE-2007-0045: Cross site scripting problems in the Acrobat Reader
		  plugin were fixed, which could be exploited by remote
		  attackers to conduct XSS attacks against any site that
		  is providing PDFs.

   CVE-2007-0046: A double free problem in the Acrobat Reader plugin was fixed
                  which could be used by remote attackers to potentially execute
   	          arbitrary code.
   	          Note that all platforms using Adobe Reader currently have
   	          counter measures against such attack where it will just
   	          cause a controlled abort().

   CVE-2007-0047 and CVE-2007-0048 affect only Microsoft Windows and
   Internet Explorer.

   Please note that the Acrobat Reader on SUSE Linux Enterprise Server
   9 is affected too, but can not be updated currently due to GTK+
   2.4 requirements.  We are trying to find a solution.

   Acrobat Reader on SUSE Linux Enterprise Server 8 and SUSE Linux
   Desktop 1 is no longer supported and should be deinstalled.

2) Solution or Work-Around

   As a workaround, you can use the free PDF readers, kpdf, xpdf, evince,
   and others.

   Please install the updated 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 10.2:
             c37b991bf98afafafe7cef049b19c432

   SUSE LINUX 10.1:
             1c2d6f4028f856b208c7a63a1a085ae2

   SUSE LINUX 10.0:
             065c5b67a4194558d70f23671f0800db

   SUSE LINUX 9.3:
             da0c72bc6379fa546f581d5b73eab620

   Sources:

   openSUSE 10.2:
             c29bf975f673b532189ced3754693ed0

   SUSE LINUX 10.1:
             6cbe0b868a4bfffa536311e933f402a2

   SUSE LINUX 10.0:
             668ca101366dc4e66cb4670de282b6be

   SUSE LINUX 9.3:
             3e8a7e56bad5c5cba050f7c69c40d5fa

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

   Novell Linux Desktop 9
     http://support.novell.com/techcenter/psdb/e4aa9329743e7c8bb35f09a113da0938.html

   SUSE SLED 10
     http://support.novell.com/techcenter/psdb/af82ce465dd28a7a87602e1069a0e963.html

______________________________________________________________________________

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:

    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
                .

    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
                .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================

SuSE: 2007-011: Acrobat Reader 7.0.9 Security Update

January 22, 2007
The Adobe Acrobat Reader has been updated to version 7.0.9

Summary


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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                acroread
        Announcement ID:        SUSE-SA:2007:011
        Date:                   Mon, 22 Jan 2007 18:00:00 +0000
        Affected Products:      SUSE LINUX 9.3
                                SUSE LINUX 10.0
                                SUSE LINUX 10.1
                                openSUSE 10.2
                                Novell Linux Desktop 9
                                SUSE SLED 10
        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-5857, CVE-2007-0044, CVE-2007-0045
                                CVE-2007-0046, CVE-2007-0047, CVE-2007-0048

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

   The Adobe Acrobat Reader has been updated to version 7.0.9.

   This update also includes following security fixes:

   CVE-2006-5857: A memory corruption problem was fixed in Adobe Acrobat
                  Reader can potentially lead to code execution.

   CVE-2007-0044: Universal Cross Site Request Forgery (CSRF) problems
		  were fixed in the Acrobat Reader plugin which could be
		  exploited by remote attackers to conduct CSRF attacks
		  using any site that is providing PDFs.

   CVE-2007-0045: Cross site scripting problems in the Acrobat Reader
		  plugin were fixed, which could be exploited by remote
		  attackers to conduct XSS attacks against any site that
		  is providing PDFs.

   CVE-2007-0046: A double free problem in the Acrobat Reader plugin was fixed
                  which could be used by remote attackers to potentially execute
   	          arbitrary code.
   	          Note that all platforms using Adobe Reader currently have
   	          counter measures against such attack where it will just
   	          cause a controlled abort().

   CVE-2007-0047 and CVE-2007-0048 affect only Microsoft Windows and
   Internet Explorer.

   Please note that the Acrobat Reader on SUSE Linux Enterprise Server
   9 is affected too, but can not be updated currently due to GTK+
   2.4 requirements.  We are trying to find a solution.

   Acrobat Reader on SUSE Linux Enterprise Server 8 and SUSE Linux
   Desktop 1 is no longer supported and should be deinstalled.

2) Solution or Work-Around

   As a workaround, you can use the free PDF readers, kpdf, xpdf, evince,
   and others.

   Please install the updated 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 10.2:
             c37b991bf98afafafe7cef049b19c432

   SUSE LINUX 10.1:
             1c2d6f4028f856b208c7a63a1a085ae2

   SUSE LINUX 10.0:
             065c5b67a4194558d70f23671f0800db

   SUSE LINUX 9.3:
             da0c72bc6379fa546f581d5b73eab620

   Sources:

   openSUSE 10.2:
             c29bf975f673b532189ced3754693ed0

   SUSE LINUX 10.1:
             6cbe0b868a4bfffa536311e933f402a2

   SUSE LINUX 10.0:
             668ca101366dc4e66cb4670de282b6be

   SUSE LINUX 9.3:
             3e8a7e56bad5c5cba050f7c69c40d5fa

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

   Novell Linux Desktop 9
     http://support.novell.com/techcenter/psdb/e4aa9329743e7c8bb35f09a113da0938.html

   SUSE SLED 10
     http://support.novell.com/techcenter/psdb/af82ce465dd28a7a87602e1069a0e963.html

______________________________________________________________________________

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:

    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
                .

    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
                .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================

References

Severity

Related News