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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                MozillaFirefox,MozillaThunderbird,seamonkey
        Announcement ID:        SUSE-SA:2006:068
        Date:                   Thu, 16 Nov 2006 18:00:00 +0000
        Affected Products:      Novell Linux Desktop 9
                                SUSE LINUX 10.1
                                SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE SLED 10
                                SUSE SLES 10
        Vulnerability Type:     remote denial of service
        Severity (1-10):        6
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-5464 CVE-2006-5747 CVE-2006-5748
                                CVE-2006-5462 CVE-2006-5463
                                MFSA2006-65 MFSA2006-66 MFSA2006-67

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             Mozilla Firefox/Thunderbird 1.5.0.8 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

   MozillaFirefox has been updated to the security update release
   1.5.0.8, MozillaThunderbird has been updated to 1.5.0.8, and the
   Mozilla Seamonkey suite has been updated to 1.0.6 to fix the following
   security issues.

   Full details of the security problems can be found on:
   https://www.mozilla.org/en-US/security/known-vulnerabilities/

   MFSA2006-65: This issue is split into 3 sub-entries, for ongoing
   stability improvements in the Mozilla browsers:
        CVE-2006-5464: Layout engine flaws were fixed.
        CVE-2006-5747: A xml.prototype.hasOwnProperty flaw was fixed.
        CVE-2006-5748: Fixes were applied to the Javascript engine.

   MFSA2006-66/CVE-2006-5462: MFSA 2006-60 reported that RSA digital
   signatures with a low exponent (typically 3) could be forged. Firefox
   and Thunderbird 1.5.0.7, which incorporated NSS version 3.10.2,
   were incompletely patched and remained vulnerable to a variant of
   this attack.

   MFSA2006-67/CVE-2006-5463: shutdown demonstrated that it was possible
   to modify a Script object while it was executing, potentially leading
   to the execution of arbitrary JavaScript bytecode.

   Note that Mozilla Suite updates for products before SUSE Linux 10.1 / SLES 10
   are not available yet due to backporting problems.

2) Solution or Work-Around

   Please install the update packages.

3) Special Instructions and Notes

   Please restart running Firefox browsers and Thunderbird Mailprograms
   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:
             a71ff28968946b9f5f418850fd89f040
             0670be80cb53f1812c1ec2111dc3d319
             582ee8d62a2265f419f3c935fd28e140
             3a697615a0d1d91bbad17744c10d5642
             038fa9aa0cc125ebcabd5056ae053e3c
             39fb09fd03477ae0b21a9465a367743e
             6e3c9353d48a8aabd5adb17abc8b8a10
             f6899d09d3d1d3e03e615a35fb33d693
             c64abb5300c18531d13095ac60197117
             6af660eae2ea7212846321fdeabc0a6c
             1a426dc987e6d1b1cc43362d5bf49c3e

   SUSE LINUX 10.0:
             e33a435adb724a5a67e3f1a6b3170079
             aba89e486b5fd093403070dad154382a
             a2781cd3c5a5afdffc786fbab2520bba

   SUSE LINUX 9.3:
             f1e93cd6d77c99c1b8085955169e4f23
             239863d6c69b11262007a86c5d5596c3
             44b9e963442b7312dc26f11795022627

   Power PC Platform:

   SUSE LINUX 10.1:
             e909d7df1cb3e4540ca0302508852874
             af32635994a6bb074f6d5e5b885ee1c6
             bf17da86409001df349ae4fbac4b668b
             f44b2d371ad12a48a989b96ed4023167
             8f5947f98696c98356313ca55ac490e8
             752591a3c37606ae0cd0bf45a615dc79
             2e819c9757969f9599a5c164c3a6580b
             4291c715903383ccc9a171e2e49ebfab
             a19f68a00db97ae677958661c9894f8d
             31be91c974e4ba3c01439180d480d274
             f2d1a5caa889b38e90364a6a4a12a980

   SUSE LINUX 10.0:
             69f4d936a8d8f11ea0dce189ed4f7f01
             a7a3bd6f9f3b4147acaf414437fcabe2
             e6ca4b911052054a45371f41abc77a70

   x86-64 Platform:

   SUSE LINUX 10.1:
             f232cb857a035182ed2d521bfd55f874
             cdb73b01ecd43204b5790ee3bf253de0
             7382f2acbf3bd3fc3aed35ca71b0d65e
             17e317ec80fa07a95fdc1f113c7417df
             525b092e5cc19e58e80d2f7e520cb554
             7ef37cf7fd80a2b40af3bb2f7ff7c665
             1705c736eeddaa6d6e4add05e727ef39
             0756bad0119aa9f282a70f71a4759a86
             b85bfb834272d99c6050bb268c4a3149

   SUSE LINUX 10.0:
             96513992769ceb5e0d4b90a9c2fda4de

   SUSE LINUX 9.3:
             7cbbc19627f55155e9f7b436b4a33527

   Sources:

   SUSE LINUX 10.1:
             e911273b221cb088d07f0413f0e22907
             5bf89c4adbb54a5e86fa03b3d6b4fde0
             a2d387652f944c0cb106310ad3502b87

   SUSE LINUX 10.0:
             ccdd21afb275385efd1fa5bee9ce2101
             8216c602629777a602bd88b7aa73c5ed

   SUSE LINUX 9.3:
             bbc1be52a5618a586e50e8cd1d1d420b
             e766484c7d8fb446bd53a20edbc1f0cc

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

   Novell Linux Desktop 9
   SUSE SLES 10
   SUSE SLED 10
     http://support.novell.com/techcenter/psdb/eb29e246d47ad02c74de06d48db89df2.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:

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

SuSE: 2006-068: Mozilla Firefox, Thunderbird, SeaMonkey Security Update

November 16, 2006
MozillaFirefox has been updated to the security update release MozillaFirefox has been updated to the security update release 1.5.0.8, MozillaThunderbird has been updated to 1.5.0....

Summary


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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                MozillaFirefox,MozillaThunderbird,seamonkey
        Announcement ID:        SUSE-SA:2006:068
        Date:                   Thu, 16 Nov 2006 18:00:00 +0000
        Affected Products:      Novell Linux Desktop 9
                                SUSE LINUX 10.1
                                SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE SLED 10
                                SUSE SLES 10
        Vulnerability Type:     remote denial of service
        Severity (1-10):        6
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-5464 CVE-2006-5747 CVE-2006-5748
                                CVE-2006-5462 CVE-2006-5463
                                MFSA2006-65 MFSA2006-66 MFSA2006-67

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             Mozilla Firefox/Thunderbird 1.5.0.8 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

   MozillaFirefox has been updated to the security update release
   1.5.0.8, MozillaThunderbird has been updated to 1.5.0.8, and the
   Mozilla Seamonkey suite has been updated to 1.0.6 to fix the following
   security issues.

   Full details of the security problems can be found on:
   https://www.mozilla.org/en-US/security/known-vulnerabilities/

   MFSA2006-65: This issue is split into 3 sub-entries, for ongoing
   stability improvements in the Mozilla browsers:
        CVE-2006-5464: Layout engine flaws were fixed.
        CVE-2006-5747: A xml.prototype.hasOwnProperty flaw was fixed.
        CVE-2006-5748: Fixes were applied to the Javascript engine.

   MFSA2006-66/CVE-2006-5462: MFSA 2006-60 reported that RSA digital
   signatures with a low exponent (typically 3) could be forged. Firefox
   and Thunderbird 1.5.0.7, which incorporated NSS version 3.10.2,
   were incompletely patched and remained vulnerable to a variant of
   this attack.

   MFSA2006-67/CVE-2006-5463: shutdown demonstrated that it was possible
   to modify a Script object while it was executing, potentially leading
   to the execution of arbitrary JavaScript bytecode.

   Note that Mozilla Suite updates for products before SUSE Linux 10.1 / SLES 10
   are not available yet due to backporting problems.

2) Solution or Work-Around

   Please install the update packages.

3) Special Instructions and Notes

   Please restart running Firefox browsers and Thunderbird Mailprograms
   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:
             a71ff28968946b9f5f418850fd89f040
             0670be80cb53f1812c1ec2111dc3d319
             582ee8d62a2265f419f3c935fd28e140
             3a697615a0d1d91bbad17744c10d5642
             038fa9aa0cc125ebcabd5056ae053e3c
             39fb09fd03477ae0b21a9465a367743e
             6e3c9353d48a8aabd5adb17abc8b8a10
             f6899d09d3d1d3e03e615a35fb33d693
             c64abb5300c18531d13095ac60197117
             6af660eae2ea7212846321fdeabc0a6c
             1a426dc987e6d1b1cc43362d5bf49c3e

   SUSE LINUX 10.0:
             e33a435adb724a5a67e3f1a6b3170079
             aba89e486b5fd093403070dad154382a
             a2781cd3c5a5afdffc786fbab2520bba

   SUSE LINUX 9.3:
             f1e93cd6d77c99c1b8085955169e4f23
             239863d6c69b11262007a86c5d5596c3
             44b9e963442b7312dc26f11795022627

   Power PC Platform:

   SUSE LINUX 10.1:
             e909d7df1cb3e4540ca0302508852874
             af32635994a6bb074f6d5e5b885ee1c6
             bf17da86409001df349ae4fbac4b668b
             f44b2d371ad12a48a989b96ed4023167
             8f5947f98696c98356313ca55ac490e8
             752591a3c37606ae0cd0bf45a615dc79
             2e819c9757969f9599a5c164c3a6580b
             4291c715903383ccc9a171e2e49ebfab
             a19f68a00db97ae677958661c9894f8d
             31be91c974e4ba3c01439180d480d274
             f2d1a5caa889b38e90364a6a4a12a980

   SUSE LINUX 10.0:
             69f4d936a8d8f11ea0dce189ed4f7f01
             a7a3bd6f9f3b4147acaf414437fcabe2
             e6ca4b911052054a45371f41abc77a70

   x86-64 Platform:

   SUSE LINUX 10.1:
             f232cb857a035182ed2d521bfd55f874
             cdb73b01ecd43204b5790ee3bf253de0
             7382f2acbf3bd3fc3aed35ca71b0d65e
             17e317ec80fa07a95fdc1f113c7417df
             525b092e5cc19e58e80d2f7e520cb554
             7ef37cf7fd80a2b40af3bb2f7ff7c665
             1705c736eeddaa6d6e4add05e727ef39
             0756bad0119aa9f282a70f71a4759a86
             b85bfb834272d99c6050bb268c4a3149

   SUSE LINUX 10.0:
             96513992769ceb5e0d4b90a9c2fda4de

   SUSE LINUX 9.3:
             7cbbc19627f55155e9f7b436b4a33527

   Sources:

   SUSE LINUX 10.1:
             e911273b221cb088d07f0413f0e22907
             5bf89c4adbb54a5e86fa03b3d6b4fde0
             a2d387652f944c0cb106310ad3502b87

   SUSE LINUX 10.0:
             ccdd21afb275385efd1fa5bee9ce2101
             8216c602629777a602bd88b7aa73c5ed

   SUSE LINUX 9.3:
             bbc1be52a5618a586e50e8cd1d1d420b
             e766484c7d8fb446bd53a20edbc1f0cc

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

   Novell Linux Desktop 9
   SUSE SLES 10
   SUSE SLED 10
     http://support.novell.com/techcenter/psdb/eb29e246d47ad02c74de06d48db89df2.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:

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

References

Severity

Related News