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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                MozillaFirefox,MozillaThunderbird,Seamonkey
        Announcement ID:        SUSE-SA:2006:048
        Date:                   Wed, 16 Aug 2006 17:00:00 +0000
        Affected Products:      Novell Linux Desktop 9
                                SLE SDK 10
                                SUSE LINUX 10.1
                                SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE LINUX 9.2
                                SUSE SLES 10
        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-3113, CVE-2006-3677, CVE-2006-3801
                                CVE-2006-3802, CVE-2006-3803, CVE-2006-3804
                                CVE-2006-3805, CVE-2006-3806, CVE-2006-3807
                                CVE-2006-3808, CVE-2006-3809, CVE-2006-3810
                                CVE-2006-3811, CVE-2006-3812, MFSA 2006-01
                                MFSA 2006-10, MFSA 2006-44, MFSA 2006-45
                                MFSA 2006-46, MFSA 2006-47, MFSA 2006-48
                                MFSA 2006-49, MFSA 2006-50, MFSA 2006-51
                                MFSA 2006-52, MFSA 2006-53, MFSA 2006-54
                                MFSA 2006-55, MFSA 2006-56

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             various mozilla browser 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

   To fix various security problems we released update packages that
   bring Mozilla Firefox to version 1.5.0.6, MozillaThunderdbird to
   version 1.5.0.5 and the Seamonkey Suite to version 1.0.3.

   Note that on Novell Linux Desktop 9 and SUSE Linux 9.2 up to 10.0
   this is a major version upgrade of Mozilla Firefox, please check if
   your Firefox plugins are still working.

   Still missing are updates for the (discontinued) Mozilla Suite.

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

   The update includes fixes to the following security problems:
   - CVE-2006-3801/MFSA 2006-44: Code execution through deleted frame reference

     Thilo Girmann discovered that in certain circumstances a JavaScript
     reference to a frame or window was not properly cleared when the
     referenced content went away, and he demonstrated that this pointer
     to a deleted object could be used to execute native code supplied
     by the attacker.

   - CVE-2006-3677/MFSA 2006-45: Javascript navigator Object Vulnerability

     An anonymous researcher for TippingPoint and the Zero Day Initiative
     showed that when used in a web page Java would reference properties
     of the window.navigator object as it started up. If the page replaced
     the navigator object before starting Java then the browser would
     crash in a way that could be exploited to run native code supplied
     by the attacker.

   - CVE-2006-3113/MFSA 2006-46: Memory corruption with simultaneous events

     Secunia Research has discovered a vulnerability in Mozilla Firefox
     1.5 branch, which can be exploited by malicious people to compromise
     a user's system.

     The vulnerability is caused due to an memory corruption error within
     the handling of simultaneously happening XPCOM events, which leads
     to use of a deleted timer object. This generally results in a crash
     but potentially could be exploited to execute arbitrary code on a
     user's system when a malicious website is visited.

   - CVE-2006-3802/MFSA 2006-47: Native DOM methods can be hijacked across
     domains

     A malicious page can hijack native DOM methods on a document object
     in another domain, which will run the attacker's script when called
     by the victim page.  This could be used to steal login cookies,
     password, or other sensitive data on the target page, or to perform
     actions on behalf of a logged-in user.

     Access checks on all other properties and document nodes are
     performed correctly. This cross-site scripting (XSS) attack is
     limited to pages which use standard DOM methods of the top-level
     document object, such as document.getElementById(). This includes
     many popular sites, especially the newer ones that offer rich
     interaction to the user.

   - CVE-2006-3803/MFSA 2006-48: JavaScript new Function race condition

     H. D. Moore reported a testcase that was able to trigger a race
     condition where JavaScript garbage collection deleted a temporary
     variable still being used in the creation of a new Function
     object. The resulting use of a deleted object may be potentially
     exploitable to run native code provided by the attacker.

   - CVE-2006-3804/MFSA 2006-49: Heap buffer overwrite on malformed VCard

     A VCard attachment with a malformed base64 field (such as a photo)
     can trigger a heap buffer overwrite. These have proven exploitable
     in the past, though in this case the overwrite is accompanied by
     an integer underflow that would attempt to copy more data than the
     typical machine has, leading to a crash.

   - CVE-2006-3805/CVE-2006-3806/MFSA 2006-50: JavaScript engine vulnerabilities

     Continuing our security audit of the JavaScript engine, Mozilla
     developers found and fixed several potential vulnerabilities.

     Igor Bukanov and shutdown found additional places where an untimely
     garbage collection could delete a temporary object that was in active
     use (similar to MFSA 2006-01 and MFSA 2006-10). Some of these may
     allow an attacker to run arbitrary code given the right conditions.

     Georgi Guninski found potential integer overflow issues with long
     strings in the toSource() methods of the Object, Array and String
     objects as well as string function arguments.

   - CVE-2006-3807/MFSA 2006-51: Privilege escalation using named-functions
     and redefined "new Object()"

     moz_bug_r_a4 discovered that named JavaScript functions have
     a parent object created using the standard Object() constructor
     (ECMA-specified behavior) and that this constructor can be redefined
     by script (also ECMA-specified behavior). If the Object() constructor
     is changed to return a reference to a privileged object with useful
     properties it is possible to have attacker-supplied script excuted
     with elevated privileges by calling the function. This could be
     used to install malware or take other malicious actions.

     Our fix involves calling the internal Object constructor which
     appears to be what other ECMA-compatible interpreters do.

   - CVE-2006-3808/MFSA 2006-52: PAC privilege escalation using
     Function.prototype.call

     moz_bug_r_a4 reports that a malicious Proxy AutoConfig (PAC)
     server could serve a PAC script that can execute code with elevated
     privileges by setting the required FindProxyForURL function to
     the eval method on a privileged object that leaked into the PAC
     sandbox. By redirecting the victim to a specially-crafted URL --
     easily done since the PAC script controls which proxy to use --
     the URL "hostname" can be executed as privileged script.

     A malicious proxy server can perform spoofing attacks on the user
     so it was already important to use a trustworthy PAC server.

   - CVE-2006-3809/MFSA 2006-53: UniversalBrowserRead privilege escalation

     shutdown reports that scripts granted the UniversalBrowserRead
     privilege can leverage that into the equivalent of the far more
     powerful UniversalXPConnect since they are allowed to "read" into
     a privileged context. This allows the attacker the ability to run
     scripts with the full privelege of the user running the browser,
     possibly installing malware or snooping on private data. This has
     been fixed so that UniversalBrowserRead and UniversalBrowserWrite
     are limited to reading from and writing into only normally-privileged
     browser windows and frames.

   - CVE-2006-3810/MFSA 2006-54: XSS with XPCNativeWrapper(window).Function(...)

     shutdown reports that cross-site scripting (XSS) attacks could be
     performed using the construct XPCNativeWrapper(window).Function(...),
     which created a function that appeared to belong to the window in
     question even after it had been navigated to the target site.

   - CVE-2006-3811/MFSA 2006-55: Crashes with evidence of memory corruption

     As part of the Firefox 1.5.0.5 stability and security release,
     developers in the Mozilla community looked for and fixed several
     crash bugs to improve the stability of Mozilla clients. Some of
     these crashes showed evidence of memory corruption that we presume
     could be exploited to run arbitrary code with enough effort.

   - CVE-2006-3812/MFSA 2006-56: chrome: scheme loading remote content

     Benjamin Smedberg discovered that chrome URL's could be made to
     reference remote files, which would run scripts with full privilege.
     There is no known way for web content to successfully load a
     chrome: url, but if a user could be convinced to do so manually
     (perhaps by copying a link and pasting it into the location bar)
     this could be exploited.

2) Solution or Work-Around

   There is no known workaround, please install the update packages.

   If you are using the old Mozilla Suite browser we recommend no longer
   using it, but switching to Mozilla Firefox, konqueror or Opera.

3) Special Instructions and Notes

   Please close and restart all running instances of Mozilla Firefox
   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:
             b077ab8d63cbca9fad680e31faa34d80
             083893020c930fb8d0d2ac107e6afcb2
             857642c909f7184dc1a6441025c57d82
             41cdd09824e46732fe0160d2eea1db13
             eecf97bedf164629445589bf5fe96f3a
             9817cd23edbe982c54e8e9788b068272
             acc5e00265da3c37d75dd8467e942523
             7a00bd110f7f36a7adac792b4d385cf2
             507c561f4179f75652550dea985fd5c5
             0e528364b0a47d8cc186be99c9273680
             0756055ab6c663c03520a566e748fd84

   SUSE LINUX 10.0:
             169195ef8d8d6aa42578c52301637a7b
             ce2ca0073cb95cd52908eca9162f12db
             82c3c849160d835d7dd2e83d58ab46ed

   SUSE LINUX 9.3:
             45252c09a02b7947e2dcff6c7b2680f7
             3f916156c178db203e19854f1be14a6e
             3878dfec4b42ebf979488794dd5ba153

   SUSE LINUX 9.2:
             1a6ec1263972cc8ee19b4b88112cbc91
             10b2b66061b686aab364255edfc7330f
             d7a39ac5e59594f326c0a7ebf893025a

   Power PC Platform:

   SUSE LINUX 10.1:
             beb4517859e09e23b1c1b8e6fe9f7f1b
             f9f7424e954609520a7dcfa5401aa6a0
             a3810db291a8575ec602046534ac0046
             1c3f6bdab05076e177c39900b8796291
             2a57cf8e9d58c738d08f3457b18c39c8
             5e5b4e2bc287c6b9fa8dcd920bd5691f
             2b6d0f991fdf834704a717a9da239114
             8130da7cdb4ece3a5b3ffcd1d8de6604
             42a37ed33a80d3a9c7922b260ec8d017
             7ed788d6b9eaaa450c7bdef217d1da0b
             22bef32ee56511c1527f2aba2686c31b

   SUSE LINUX 10.0:
             7088063ef61fef41e8ae463017bc2e7a
             1179980ccb74d1268981a991ea99ef76
             50989117d508769abe562192f7a29ac0

   x86-64 Platform:

   SUSE LINUX 10.1:
             c3c35689ec4183a3f65eadefe0e035f9
             c2a68df8c7a37edb184de0d816bc6f40
             2c9f593099e65d8a4bea1ddb4475b51b
             546d70365782daeae85bc2a5e042bae6
             1b985d53285222446923fb37d936d759
             c81a87ba73ed766dc25f2b89b98f4f8e
             36ca5818bb717578542d7def4b8724f9
             2c798a9aa382ff0bc6f0d44c1861156d
             b6f3a089873cf2df5d82e7fcc4943b28

   SUSE LINUX 10.0:
             64b491ee5e76fd81d22e6bc03efe6b86

   SUSE LINUX 9.3:
             5f797b743baa880b609350dce4003e28

   SUSE LINUX 9.2:
             02d00c594d85c27901ac8975ff4074b5
             c3e1ab3e8bffa3b7fd1f8c93253bd387
             409577b2b376df93980071fa6b080638

   Sources:

   SUSE LINUX 10.1:
             8052f82d870aa163544f20fb0e6e2a7e
             a6cc091a2379e066d89f30cc4ef4daca
             22f8c43051e3f87df2f6c892259b84c1

   SUSE LINUX 10.0:
             b369c54440dab641eaca7ffacce2fdca
             3d8939c81652438cc45df2dfafad3401

   SUSE LINUX 9.3:
             6e343044e7c9061e7893d1ad798fb683
             520ad8710e85f56082e8f744dd7fa9b4

   SUSE LINUX 9.2:
             e102231a46d19c0d05f6e31318a6527e
             206929deb348a7ca699d92cda0e4c3e1

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

   SUSE SLES 10
     
   SLE SDK 10
     
   SUSE SLE 10 DEBUGINFO
     
   Novell Linux Desktop 9 for x86
     
______________________________________________________________________________

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-048: MozillaFirefox, MozillaThunderbird, Seamonkey Security Update

August 16, 2006
To fix various security problems we released update packages that To fix various security problems we released update packages that bring Mozilla Firefox to version 1.5.0.6, Mozill...

Summary


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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                MozillaFirefox,MozillaThunderbird,Seamonkey
        Announcement ID:        SUSE-SA:2006:048
        Date:                   Wed, 16 Aug 2006 17:00:00 +0000
        Affected Products:      Novell Linux Desktop 9
                                SLE SDK 10
                                SUSE LINUX 10.1
                                SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE LINUX 9.2
                                SUSE SLES 10
        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-3113, CVE-2006-3677, CVE-2006-3801
                                CVE-2006-3802, CVE-2006-3803, CVE-2006-3804
                                CVE-2006-3805, CVE-2006-3806, CVE-2006-3807
                                CVE-2006-3808, CVE-2006-3809, CVE-2006-3810
                                CVE-2006-3811, CVE-2006-3812, MFSA 2006-01
                                MFSA 2006-10, MFSA 2006-44, MFSA 2006-45
                                MFSA 2006-46, MFSA 2006-47, MFSA 2006-48
                                MFSA 2006-49, MFSA 2006-50, MFSA 2006-51
                                MFSA 2006-52, MFSA 2006-53, MFSA 2006-54
                                MFSA 2006-55, MFSA 2006-56

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             various mozilla browser 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

   To fix various security problems we released update packages that
   bring Mozilla Firefox to version 1.5.0.6, MozillaThunderdbird to
   version 1.5.0.5 and the Seamonkey Suite to version 1.0.3.

   Note that on Novell Linux Desktop 9 and SUSE Linux 9.2 up to 10.0
   this is a major version upgrade of Mozilla Firefox, please check if
   your Firefox plugins are still working.

   Still missing are updates for the (discontinued) Mozilla Suite.

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

   The update includes fixes to the following security problems:
   - CVE-2006-3801/MFSA 2006-44: Code execution through deleted frame reference

     Thilo Girmann discovered that in certain circumstances a JavaScript
     reference to a frame or window was not properly cleared when the
     referenced content went away, and he demonstrated that this pointer
     to a deleted object could be used to execute native code supplied
     by the attacker.

   - CVE-2006-3677/MFSA 2006-45: Javascript navigator Object Vulnerability

     An anonymous researcher for TippingPoint and the Zero Day Initiative
     showed that when used in a web page Java would reference properties
     of the window.navigator object as it started up. If the page replaced
     the navigator object before starting Java then the browser would
     crash in a way that could be exploited to run native code supplied
     by the attacker.

   - CVE-2006-3113/MFSA 2006-46: Memory corruption with simultaneous events

     Secunia Research has discovered a vulnerability in Mozilla Firefox
     1.5 branch, which can be exploited by malicious people to compromise
     a user's system.

     The vulnerability is caused due to an memory corruption error within
     the handling of simultaneously happening XPCOM events, which leads
     to use of a deleted timer object. This generally results in a crash
     but potentially could be exploited to execute arbitrary code on a
     user's system when a malicious website is visited.

   - CVE-2006-3802/MFSA 2006-47: Native DOM methods can be hijacked across
     domains

     A malicious page can hijack native DOM methods on a document object
     in another domain, which will run the attacker's script when called
     by the victim page.  This could be used to steal login cookies,
     password, or other sensitive data on the target page, or to perform
     actions on behalf of a logged-in user.

     Access checks on all other properties and document nodes are
     performed correctly. This cross-site scripting (XSS) attack is
     limited to pages which use standard DOM methods of the top-level
     document object, such as document.getElementById(). This includes
     many popular sites, especially the newer ones that offer rich
     interaction to the user.

   - CVE-2006-3803/MFSA 2006-48: JavaScript new Function race condition

     H. D. Moore reported a testcase that was able to trigger a race
     condition where JavaScript garbage collection deleted a temporary
     variable still being used in the creation of a new Function
     object. The resulting use of a deleted object may be potentially
     exploitable to run native code provided by the attacker.

   - CVE-2006-3804/MFSA 2006-49: Heap buffer overwrite on malformed VCard

     A VCard attachment with a malformed base64 field (such as a photo)
     can trigger a heap buffer overwrite. These have proven exploitable
     in the past, though in this case the overwrite is accompanied by
     an integer underflow that would attempt to copy more data than the
     typical machine has, leading to a crash.

   - CVE-2006-3805/CVE-2006-3806/MFSA 2006-50: JavaScript engine vulnerabilities

     Continuing our security audit of the JavaScript engine, Mozilla
     developers found and fixed several potential vulnerabilities.

     Igor Bukanov and shutdown found additional places where an untimely
     garbage collection could delete a temporary object that was in active
     use (similar to MFSA 2006-01 and MFSA 2006-10). Some of these may
     allow an attacker to run arbitrary code given the right conditions.

     Georgi Guninski found potential integer overflow issues with long
     strings in the toSource() methods of the Object, Array and String
     objects as well as string function arguments.

   - CVE-2006-3807/MFSA 2006-51: Privilege escalation using named-functions
     and redefined "new Object()"

     moz_bug_r_a4 discovered that named JavaScript functions have
     a parent object created using the standard Object() constructor
     (ECMA-specified behavior) and that this constructor can be redefined
     by script (also ECMA-specified behavior). If the Object() constructor
     is changed to return a reference to a privileged object with useful
     properties it is possible to have attacker-supplied script excuted
     with elevated privileges by calling the function. This could be
     used to install malware or take other malicious actions.

     Our fix involves calling the internal Object constructor which
     appears to be what other ECMA-compatible interpreters do.

   - CVE-2006-3808/MFSA 2006-52: PAC privilege escalation using
     Function.prototype.call

     moz_bug_r_a4 reports that a malicious Proxy AutoConfig (PAC)
     server could serve a PAC script that can execute code with elevated
     privileges by setting the required FindProxyForURL function to
     the eval method on a privileged object that leaked into the PAC
     sandbox. By redirecting the victim to a specially-crafted URL --
     easily done since the PAC script controls which proxy to use --
     the URL "hostname" can be executed as privileged script.

     A malicious proxy server can perform spoofing attacks on the user
     so it was already important to use a trustworthy PAC server.

   - CVE-2006-3809/MFSA 2006-53: UniversalBrowserRead privilege escalation

     shutdown reports that scripts granted the UniversalBrowserRead
     privilege can leverage that into the equivalent of the far more
     powerful UniversalXPConnect since they are allowed to "read" into
     a privileged context. This allows the attacker the ability to run
     scripts with the full privelege of the user running the browser,
     possibly installing malware or snooping on private data. This has
     been fixed so that UniversalBrowserRead and UniversalBrowserWrite
     are limited to reading from and writing into only normally-privileged
     browser windows and frames.

   - CVE-2006-3810/MFSA 2006-54: XSS with XPCNativeWrapper(window).Function(...)

     shutdown reports that cross-site scripting (XSS) attacks could be
     performed using the construct XPCNativeWrapper(window).Function(...),
     which created a function that appeared to belong to the window in
     question even after it had been navigated to the target site.

   - CVE-2006-3811/MFSA 2006-55: Crashes with evidence of memory corruption

     As part of the Firefox 1.5.0.5 stability and security release,
     developers in the Mozilla community looked for and fixed several
     crash bugs to improve the stability of Mozilla clients. Some of
     these crashes showed evidence of memory corruption that we presume
     could be exploited to run arbitrary code with enough effort.

   - CVE-2006-3812/MFSA 2006-56: chrome: scheme loading remote content

     Benjamin Smedberg discovered that chrome URL's could be made to
     reference remote files, which would run scripts with full privilege.
     There is no known way for web content to successfully load a
     chrome: url, but if a user could be convinced to do so manually
     (perhaps by copying a link and pasting it into the location bar)
     this could be exploited.

2) Solution or Work-Around

   There is no known workaround, please install the update packages.

   If you are using the old Mozilla Suite browser we recommend no longer
   using it, but switching to Mozilla Firefox, konqueror or Opera.

3) Special Instructions and Notes

   Please close and restart all running instances of Mozilla Firefox
   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:
             b077ab8d63cbca9fad680e31faa34d80
             083893020c930fb8d0d2ac107e6afcb2
             857642c909f7184dc1a6441025c57d82
             41cdd09824e46732fe0160d2eea1db13
             eecf97bedf164629445589bf5fe96f3a
             9817cd23edbe982c54e8e9788b068272
             acc5e00265da3c37d75dd8467e942523
             7a00bd110f7f36a7adac792b4d385cf2
             507c561f4179f75652550dea985fd5c5
             0e528364b0a47d8cc186be99c9273680
             0756055ab6c663c03520a566e748fd84

   SUSE LINUX 10.0:
             169195ef8d8d6aa42578c52301637a7b
             ce2ca0073cb95cd52908eca9162f12db
             82c3c849160d835d7dd2e83d58ab46ed

   SUSE LINUX 9.3:
             45252c09a02b7947e2dcff6c7b2680f7
             3f916156c178db203e19854f1be14a6e
             3878dfec4b42ebf979488794dd5ba153

   SUSE LINUX 9.2:
             1a6ec1263972cc8ee19b4b88112cbc91
             10b2b66061b686aab364255edfc7330f
             d7a39ac5e59594f326c0a7ebf893025a

   Power PC Platform:

   SUSE LINUX 10.1:
             beb4517859e09e23b1c1b8e6fe9f7f1b
             f9f7424e954609520a7dcfa5401aa6a0
             a3810db291a8575ec602046534ac0046
             1c3f6bdab05076e177c39900b8796291
             2a57cf8e9d58c738d08f3457b18c39c8
             5e5b4e2bc287c6b9fa8dcd920bd5691f
             2b6d0f991fdf834704a717a9da239114
             8130da7cdb4ece3a5b3ffcd1d8de6604
             42a37ed33a80d3a9c7922b260ec8d017
             7ed788d6b9eaaa450c7bdef217d1da0b
             22bef32ee56511c1527f2aba2686c31b

   SUSE LINUX 10.0:
             7088063ef61fef41e8ae463017bc2e7a
             1179980ccb74d1268981a991ea99ef76
             50989117d508769abe562192f7a29ac0

   x86-64 Platform:

   SUSE LINUX 10.1:
             c3c35689ec4183a3f65eadefe0e035f9
             c2a68df8c7a37edb184de0d816bc6f40
             2c9f593099e65d8a4bea1ddb4475b51b
             546d70365782daeae85bc2a5e042bae6
             1b985d53285222446923fb37d936d759
             c81a87ba73ed766dc25f2b89b98f4f8e
             36ca5818bb717578542d7def4b8724f9
             2c798a9aa382ff0bc6f0d44c1861156d
             b6f3a089873cf2df5d82e7fcc4943b28

   SUSE LINUX 10.0:
             64b491ee5e76fd81d22e6bc03efe6b86

   SUSE LINUX 9.3:
             5f797b743baa880b609350dce4003e28

   SUSE LINUX 9.2:
             02d00c594d85c27901ac8975ff4074b5
             c3e1ab3e8bffa3b7fd1f8c93253bd387
             409577b2b376df93980071fa6b080638

   Sources:

   SUSE LINUX 10.1:
             8052f82d870aa163544f20fb0e6e2a7e
             a6cc091a2379e066d89f30cc4ef4daca
             22f8c43051e3f87df2f6c892259b84c1

   SUSE LINUX 10.0:
             b369c54440dab641eaca7ffacce2fdca
             3d8939c81652438cc45df2dfafad3401

   SUSE LINUX 9.3:
             6e343044e7c9061e7893d1ad798fb683
             520ad8710e85f56082e8f744dd7fa9b4

   SUSE LINUX 9.2:
             e102231a46d19c0d05f6e31318a6527e
             206929deb348a7ca699d92cda0e4c3e1

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

   SUSE SLES 10
     
   SLE SDK 10
     
   SUSE SLE 10 DEBUGINFO
     
   Novell Linux Desktop 9 for x86
     
______________________________________________________________________________

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