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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                mozilla
        Announcement ID:        SUSE-SA:2007:006
        Date:                   Fri, 12 Jan 2007 13:00:00 +0000
        Affected Products:      Novell Linux Desktop 9
                                Novell Linux POS 9
                                Open Enterprise Server
                                SUSE LINUX 10.1
                                SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE SLES 9
        Vulnerability Type:     remote denial of service
        Severity (1-10):        6
        SUSE Default Package:   no
        Cross-References:       CVE-2006-6497, CVE-2006-6498, CVE-2006-6499
                                CVE-2006-6500, CVE-2006-6501, CVE-2006-6502
                                CVE-2006-6503, CVE-2006-6504, CVE-2006-6505
                                CVE-2006-6506, CVE-2006-6507

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             various mozilla/seamonkey suite security problems
           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

   A number of security issues have been fixed in the Mozilla browser
   suite, which could be used by remote attackers to gain privileges,
   access to confidential information or cause denial of service attacks.

   Since the Mozilla Suite 1.7 branch is no longer maintained this
   update most of our older products to use the Mozilla Seamonkey Suite
   version 1.0.7.

   Security issues we fixed (compared from last seamonkey update round
   only) are listed below. More Details regarding the problems can be
   found on this page:
       https://www.mozilla.org/en-US/security/known-vulnerabilities/

   The updated packages includes fixes for the following security problems:
   CVE-2006-6497/MFSA-2006-68: Crashes with evidence of memory corruption
                               were fixed in the layout engine.
   CVE-2006-6498/MFSA-2006-68: Crashes with evidence of memory corruption
                               were fixed in the javascript engine.
   CVE-2006-6499/MFSA-2006-68: Crashes regarding floating point usage
                               were fixed. Linux is not affected.
   CVE-2006-6501/MFSA-2006-70: A privilege escalation using a watch
                               point was fixed.
   CVE-2006-6502/MFSA-2006-71: A LiveConnect crash finalizing JS objects
                               was fixed.
   CVE-2006-6503/MFSA-2006-72: A XSS problem caused by setting img.src
                               to javascript: URI was fixed.
   CVE-2006-6504/MFSA-2006-73: A Mozilla SVG Processing Remote Code
                               Execution was fixed.
   CVE-2006-6505/MFSA-2006-74: Some Mail header processing heap overflows
                               were fixed.
   CVE-2006-6506/MFSA-2006-75: The RSS Feed-preview referrer leak
                               was fixed.
   CVE-2006-6507/MFSA-2006-76: A XSS problem using outer window's Function
                               object was fixed.

   Problems with these packages we could not fix yet:

   - On SUSE Linux Desktop 1.0 the upgrade was not possible yet due
     to library inter-dependencies problems between Mozilla and GTK+.

     We recommend deinstalling mozilla on this product.

   - The SUSE Linux Enterprise Server 8 update has shown regressions
     in flash and java plugin handling which we are investigating.

   - On SUSE Linux 10.0 epiphany stops working for still unknown reasons.

     We are investigating this and recommend using mozilla or
     MozillaFirefox directly instead.

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 mozilla or seamonkey 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:
             691bd7a6105e6f3b400b1bfd02c7ffa4
             0fea4d7bc71c91d3f94b5bc97d254c30
             eceb85212935d502085aa018044c97d8
             4356126f6103052702b4756a3f2cd3d3
             e540d5c771f876329538869bdfc8e774
             6e0d898204995310a7fe96f13853e9fc
             b4a7fd442c5978b1f28d3e21c994a9bd

   SUSE LINUX 10.0:
             e733f6ac215ef300e4e83b85eedb254b
             8e7abfedb813376b695115c7caa09077
             2fe75e720667ad437f83b1b8c11606ba
             df92c79d27ecf653875e737b974b6812
             0bf3ef7649c0b9033635f51d0ae66acc
             9845b9d2181e55f107e264c5cc191e11
             1cd171a482a8a1f13c9d73542589a79e
             cfc891f616d49ec435c8f0389b976d54
             895026932bf0256f7365d1ad8280e162
             5336b79760646a54a993549b10debfaf
             2e8ec85326ae2560ac9cc15497c35d00
             5a20cd21dd6bc3669a1e33361de53a53
             f988e7c897989e7324a6c017736ef57f
             4bc1d88408f3e0b2bad372fa07ce7201
             e9cbf5c734d3c70f491d79490a20310c

   SUSE LINUX 9.3:
             0e7a1b299096d375311435328c3997a6
             957d285ff06fb55cfeb1de3cec7209ae
             1aa65804a1270b60fc772a206ab3d5a6
             9bccb9dafe859004164fbc6c7804d04b
             89501dfa754cf96cd1cf37c13785d608
             57fde43d64c8a3351c2cd9634baee55f
             ae8176d7d3494727f3d5c0f06cb7c077
             990b479cab2811454c9fcc4cec2a0131
             5718139893acb38955196693309c866e
             8d1c58c7fb1f063f7e73ca9ecb6dec13
             b397d1ffc1a2656000bf5563a15ee354
             53c00bd80891aa53cee9dde05fbb27f1
             495d9e356bf0a986c08d90c53c7805fd
             17c74d61a654aa7083994a9f9ca7d035
             2aeff8778be93bfe272d99c66671e78f

   Power PC Platform:

   SUSE LINUX 10.1:
             8160b6918aa587d916b538086c389fcc
             63148011fb308f3675e46c22adccd914
             061903ab82cfaa6a46873e1ebbbda9e6
             6ca2d653168d7fcca0143576b9e325d9
             9df10fe0995f46532e2e024dd13aa3fa
             9112df7f324382cfbfe2ad520f7ec18c
             386dda81b7e91d9a97a89da2ec72931e

   SUSE LINUX 10.0:
             94cbfaabbe32ce4e8543331b0e211933
             bb9cfd5c0964dae6bdfb5f0bbb3a9220
             169fb5a254276fac2d33e21d4e5fc074
             f4d5402979033ab63e3c28dc4301de8d
             368be097a91fc56a7093bd5283c45274
             8e5649cd7f33dd2f3eb682019d9e6c9f
             a456e4e03b151c3b74b45e17afe4b45c
             e9a8b25e84c86ed1a6f4ca1870a5a80c
             d9495a726ad5f26e3bf9f72685ba0a20
             e8423d17e7d3ab2c4b414e388202807a
             01293213124d473733ab4f28a3b7e76c
             b807072846d59157d5bdb7cd77e0fa8a
             4f7b7f89a0b38bfb8c68a8fa2b5c8d1b
             9433f71970cb8ed4cdcc0d9c4e99ee8d
             b9ae9999cf3d911fce07005379d1c7e2

   x86-64 Platform:

   SUSE LINUX 10.1:
             1fa7f3f74e08d3e00f854f18fa307cbc
             754706dd2258a5c82f0064e8625d600d
             3031264a90c2fe4a22d194d201b24fbc
             d10bfc48aa0a7c51dbac4cbf3440486f
             25eb261c46317af23c77fda4e136188d
             1d7483a0b18dd19e29d9e21b03b37dc5
             c08dbce9626f91b2f3c14e928aac6491

   SUSE LINUX 10.0:
             e600623e759336556a4be1f2a987cda8
             d7e7b62ad5088b152807a2069217fca7
             01802f141f774601475486b2ac644111
             9121623c27dd5bbdb05cbecf3e52b611
             4e509e792eab1dfed197d18e3bb16724
             50e2e436a6e465f2d6e1887511f09380
             b70bc4c1cd197d75d43dffe7443d445d
             d6741db2d323cc114290ce861e88565f
             d86e6a32b762af18198ef459887abfec
             b863e5ff89252b9aa467a77c166792a3
             e48adaed5f275ac7441f9788bc94e50d
             2b755a27b1020db97ff3ee3f78008572
             d465da6f8fb7b5b31e2aa502b28a4203
             c1c918deb3ac00ece7493e69612dbe90
             179cc90ce6833f6ec5fc09faf368f03d

   SUSE LINUX 9.3:
             6a7e3da1c8b99d77978f60be5d708c1c
             827d70dbe55edb1b0442335f76aa7a06
             103efd565bfb50fb8247fb926666c50e
             327d71eacdf8c067cbfbd4eecde00517
             8978d235b2e1d3f1d0e1d590445f69ae
             16459e0004cf97ca397f1071fcc494c1
             3125276df0456ff87a8648c13f000971
             e5e49a8f5b1c4b5df75296f2cbe79738
             531aac2cde8e0c3a00df57670bbcd877
             3e3fe004ecb9967d4659d34f71fc179d
             53a09dc52ea7f00a051d94f0c1b5396d
             2093c833325dc4a51bf943077ef75d23
             c280a797a277445f92942dc29da9724e
             f63c5575c0413ae258f5919ac7b7d1ad
             f8763e4d083d6c590f863713dc2753d7
             c0085d1167554a15f5ed899afca245c3

   Sources:

   SUSE LINUX 10.1:
             1ae24878aac47b6a85eaee457896b2d8

   SUSE LINUX 10.0:
             41ba75d370bfb3d43066fcc8eae44aad
             845e24b32a1e202b9283c6b62fcfba46
             58332e241f66168ca90f86ef8825a8b5
             3ef701bba73faa82b330be60b324d5af
             edcf8f83a99a8bdd583f601806a0e5fb
             e1df6bf13764c2644e51ec0099acb2a5
             0d8ff5e18a378c40ab329466039c4673

   SUSE LINUX 9.3:
             198e2742a00ef781837f0c4d695bba97
             26bbda402bcd800c3377ea03052984f2
             6b8fc1af805b3672cc9dbd2b8be6205e
             dd0fb0962af4accfae631a35d35d70ca
             5dff3834434d550d271a004d3e0315f6
             fad96a1dc7da8a786fd953dffc673068
             d3bf5b983708d7e796a0280812a1a325

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

   Open Enterprise Server
     http://support.novell.com/techcenter/psdb/23c2f7e232f2a20be862d4cbaf1e30e5.html

   Novell Linux POS 9
     http://support.novell.com/techcenter/psdb/23c2f7e232f2a20be862d4cbaf1e30e5.html

   Novell Linux Desktop 9
     http://support.novell.com/techcenter/psdb/7abef1462ebc9ce70a2931e6f4f8e38b.html
     http://support.novell.com/techcenter/psdb/23c2f7e232f2a20be862d4cbaf1e30e5.html

   SUSE SLES 9
     http://support.novell.com/techcenter/psdb/23c2f7e232f2a20be862d4cbaf1e30e5.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.
    ====================================================================