SuSE: 2007-002: mono-web ASP.net sourcecode disclosure Security Upd...


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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                mono-web
        Announcement ID:        SUSE-SA:2007:002
        Date:                   Thu, 04 Jan 2007 18:00:00 +0000
        Affected Products:      openSUSE 10.2
                                SLE SDK 10
                                SUSE LINUX 10.1
                                SUSE SLED 10
                                SUSE SLES 10
        Vulnerability Type:     remote source code disclosure
        Severity (1-10):        4
        SUSE Default Package:   no
        Cross-References:       CVE-2006-6104

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             ASP.net source code disclosure
           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 security problem was found and fixed in the Mono / C# web server
   implementation.

   By appending spaces to URLs attackers could download the source code
   of ASP.net scripts that would normally get executed by the web server.

   This issue is tracked by the Mitre CVE ID CVE-2006-6104 and only
   affects SUSE Linux 10.1, openSUSE 10.2 and SUSE Linux Enterprise 10.

   Older products are not affected.

   The updated packages for this problem were released on December 29th 2006.

2) Solution or Work-Around

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

3) Special Instructions and Notes

   None.

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:
             7871ea91da68edfcd0b33e1a65f89414
             4dea03120df7e27db52f24e3453218d3
             7129007767134eee66ab5f48789fa6b8
             4aaffb7e159d5e9d0807dcbaa57f9e97
             764d536b04339d426cda40faca9e738f
             a575de3f3340abb11283aaea3d6ccda4
             22667d583ed22211edb7608de92b6979
             1d4a805666f53d39c2150894ff72312e
             c7ae739f8bb04eb013daee44967e3589
             94b8c2fa29d1684d1d93368fc289131d
             6c9392ee56d2b8aa357c52d6f49b46a4
             5ce60c49f5109ef6a869c0c3d1b5facd
             b5723ee0fae44b0de7ee7f4e98625ca5
             5668807cb61dbdd3a46da9f0154a13dc
             2f3c091bafb9c174205b9917a1c948e0
             3f6b3be8eb8ed73d8a0b8348fdfcf4fc

   SUSE LINUX 10.1:
             7e411b0255e4b8364e1fa2e261d177bb
             59c0e03583c5d59157b35c33a68ff610
             eb2b47003b0232d63dcf60a54371da59
             e115c6e2da3c2b1ccfd7177752237239
             42e8bbae01de311597b5166837ac06e1
             c3ebfde89466f76d1018afbbc2a1410e
             f6ba40eb9f4529405f21a2c5d0b39a01
             1018446b35dfd46b2404c12711b4e866
             7b864e4a21da1d12c171e168597249cb
             86ef906b744853c4b26a266cfc7460f7
             37ece2cc4d73f6b55ef0b4cc6e42f006
             c4c64d22660f77da3809a6c6d4375500
             291ccf1005505b87f59c4ab3e2acb6a5
             0d76aa220a6772796f64a058b010d90b
             4a90129294c6cd3cae2e5bd3b46e22c4
             8037c8dbfe7d5d72b918035553751d70
             b0333ba342c5f31e9c7d154f160faa8e

   Platform Independent:

   openSUSE 10.2:
             563582c657915b15b4081b6f36ee37cf

   Power PC Platform:

   openSUSE 10.2:
             7ab0a3e1908b2ce41ce6991392c56b5a
             533e9f3a2a97fe56749f3409bbd1e577
             7388cf8363ef7b6d4d2ce495276c9b3d
             70833baf535bce3b2192c705266c20ea
             51dca3ae3f5d0276ad1a67702870adf0
             12a03dd8b94fb0d2cfd25266fd4d6021
             5fca596e3bb72c03dfe8ed697a79217f
             78fc0723c0f9be7db965583a24125b27
             065affeebf284637dc17663cf647505c
             fa9b85abb2a4d7f7b8434dfaaa88e629
             b6062113f1c076e53b7bb714855e4f67
             4bd211e6f9fb5f23c681179a96641b86
             e65f00cc0a931ee23ea35cbfb0dbd567
             6cba2323367c90475a9aaf3059dba127
             88760a5f5b8a47209239ffbc3c06251d
             f2abba637b11bbf630a6796e74cc4b76

   SUSE LINUX 10.1:
             df2f559a7c5971466d4e2e56610cc474
             e25fbded3d1d80e1558b6d41dd967518
             4171575ffdd03b5711b4ead378849456
             bc13a69c38e1d5cf583b31dfd6913b47
             3554bf92b4f2febcadb50f4b29f23acc
             7f1f5caae871c29169f1c76b5b7dd718
             fe1a9b37ce0079e9c65830607403aaac
             a1aaa83c1c9d151bb79eed446ea5c7a1
             682dfb340b1cfd4fc5518e62e76a5ee8
             37574a7a9be6736bd4f703e23ef2a1d3
             3e9314db61dc553c95582be0b5da22a4
             334b918e3281772f5bae84fde6b829a9
             83af7ef9f3fe0218b3d16ed662d9bcd4
             766583abd69fcf242e3ff1f6c562ea5e
             a0a6c098484a9bb70f0242844188f52d
             f98c8ccce8bb938fb325d779d7b971c6
             5d49531a71b940ca4958485e9fee72f1

   x86-64 Platform:

   openSUSE 10.2:
             23591c785aaef10d3b422eebebbb1499
             f090dfa3c21f4071ac7312bfa0c76512
             9af61b7d487a6025107dfabf76b1d307
             d8b8ff18dfe16e6b8a4e7eea39b46fdc
             46d10714bd4534d578564b521cc4e5ee
             3352eb7cae2644d12b2761d4280f6a31
             8dcb7cd3e271a1a0bcbe843269ee8b52
             be734ae165180a801f35d26811a5a5c4
             d958bf9cdae6c32bb1e1c36df74fc9fb
             c9429b316e6eecb6ddc2682d01e170dc
             67567fd44fc1b7f3589ad48f31dd87ad
             3b95cb4747ac42848e2daf543622770c
             97fbb5843ff11f35edc5c54338d0ceb9
             46d10243690c90812ced6b1a9d5aa041
             0cfe47db6079f91b99f6fea86696d019
             34e0a3027a6db5adb8a10560467a651e
             6fbe5c405768ae26f9c00b9e6a353352

   SUSE LINUX 10.1:
             2019045021a97b167ea99ac0c046b101
             4889570b65d8eed1283146d1adbef2c5
             3b3337acb365adeb2cdd167dc8ab11c3
             54d0899c5591c4b546a4328aa023e455
             d61a5d6b3ad1418ae8828c632c38753f
             043514968a409980de9c26bb326bcf61
             79d4a0e1a3ee4ead9c32f2f2a994a3dd
             b094e7fc68ac93c8cea50dd8c9c9f8fa
             57eca0584754764c9676f64a99318eda
             2a3bf582c8bf3b3f0e3b659b5a69fa8f
             e7df071bb25de0dadd8d91d1266e813b
             ccb9cf8b02a3684bc523b1c8deafa132
             e002218ccb079ab3b98c10c6a98e6632
             b8d6933ae2cd19aae0333385c6df7179
             7d0b549bd3ff3e55363dce19060797e1
             f904919d8bb75ca477a580dc5483209d
             4c3d083e708e17e0747e98d605cf2445
             acfe0ccbdf408e2800b2410b7f7f38b6

   Sources:

   openSUSE 10.2:
             4d7e3741dccd7caa42bdc630dfe258fa
             4165d9c7bfe3e9fe270a881a152d280a

   SUSE LINUX 10.1:
             24e736054c58c12f64133037a8cf2f10

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

   SUSE SLES 10
     http://support.novell.com/techcenter/psdb/42c27df99955c5253c97cbbfb7b56d6f.html

   SLE SDK 10
     http://support.novell.com/techcenter/psdb/42c27df99955c5253c97cbbfb7b56d6f.html

   SUSE SLED 10
     http://support.novell.com/techcenter/psdb/42c27df99955c5253c97cbbfb7b56d6f.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.
    ====================================================================

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: mono-web Announcement ID: SUSE-SA:2007:002 Date: Thu, 04 Jan 2007 18:00:00 +0000 Affected Products: openSUSE 10.2 SLE SDK 10 SUSE LINUX 10.1 SUSE SLED 10 SUSE SLES 10 Vulnerability Type: remote source code disclosure Severity (1-10): 4 SUSE Default Package: no Cross-References: CVE-2006-6104 Content of This Advisory: 1) Security Vulnerability Resolved: ASP.net source code disclosure 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 security problem was found and fixed in the Mono / C# web server implementation. By appending spaces to URLs attackers could download the source code of ASP.net scripts that would normally get executed by the web server. This issue is tracked by the Mitre CVE ID CVE-2006-6104 and only affects SUSE Linux 10.1, openSUSE 10.2 and SUSE Linux Enterprise 10. Older products are not affected. The updated packages for this problem were released on December 29th 2006. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes None. 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: 7871ea91da68edfcd0b33e1a65f89414 4dea03120df7e27db52f24e3453218d3 7129007767134eee66ab5f48789fa6b8 4aaffb7e159d5e9d0807dcbaa57f9e97 764d536b04339d426cda40faca9e738f a575de3f3340abb11283aaea3d6ccda4 22667d583ed22211edb7608de92b6979 1d4a805666f53d39c2150894ff72312e c7ae739f8bb04eb013daee44967e3589 94b8c2fa29d1684d1d93368fc289131d 6c9392ee56d2b8aa357c52d6f49b46a4 5ce60c49f5109ef6a869c0c3d1b5facd b5723ee0fae44b0de7ee7f4e98625ca5 5668807cb61dbdd3a46da9f0154a13dc 2f3c091bafb9c174205b9917a1c948e0 3f6b3be8eb8ed73d8a0b8348fdfcf4fc SUSE LINUX 10.1: 7e411b0255e4b8364e1fa2e261d177bb 59c0e03583c5d59157b35c33a68ff610 eb2b47003b0232d63dcf60a54371da59 e115c6e2da3c2b1ccfd7177752237239 42e8bbae01de311597b5166837ac06e1 c3ebfde89466f76d1018afbbc2a1410e f6ba40eb9f4529405f21a2c5d0b39a01 1018446b35dfd46b2404c12711b4e866 7b864e4a21da1d12c171e168597249cb 86ef906b744853c4b26a266cfc7460f7 37ece2cc4d73f6b55ef0b4cc6e42f006 c4c64d22660f77da3809a6c6d4375500 291ccf1005505b87f59c4ab3e2acb6a5 0d76aa220a6772796f64a058b010d90b 4a90129294c6cd3cae2e5bd3b46e22c4 8037c8dbfe7d5d72b918035553751d70 b0333ba342c5f31e9c7d154f160faa8e Platform Independent: openSUSE 10.2: 563582c657915b15b4081b6f36ee37cf Power PC Platform: openSUSE 10.2: 7ab0a3e1908b2ce41ce6991392c56b5a 533e9f3a2a97fe56749f3409bbd1e577 7388cf8363ef7b6d4d2ce495276c9b3d 70833baf535bce3b2192c705266c20ea 51dca3ae3f5d0276ad1a67702870adf0 12a03dd8b94fb0d2cfd25266fd4d6021 5fca596e3bb72c03dfe8ed697a79217f 78fc0723c0f9be7db965583a24125b27 065affeebf284637dc17663cf647505c fa9b85abb2a4d7f7b8434dfaaa88e629 b6062113f1c076e53b7bb714855e4f67 4bd211e6f9fb5f23c681179a96641b86 e65f00cc0a931ee23ea35cbfb0dbd567 6cba2323367c90475a9aaf3059dba127 88760a5f5b8a47209239ffbc3c06251d f2abba637b11bbf630a6796e74cc4b76 SUSE LINUX 10.1: df2f559a7c5971466d4e2e56610cc474 e25fbded3d1d80e1558b6d41dd967518 4171575ffdd03b5711b4ead378849456 bc13a69c38e1d5cf583b31dfd6913b47 3554bf92b4f2febcadb50f4b29f23acc 7f1f5caae871c29169f1c76b5b7dd718 fe1a9b37ce0079e9c65830607403aaac a1aaa83c1c9d151bb79eed446ea5c7a1 682dfb340b1cfd4fc5518e62e76a5ee8 37574a7a9be6736bd4f703e23ef2a1d3 3e9314db61dc553c95582be0b5da22a4 334b918e3281772f5bae84fde6b829a9 83af7ef9f3fe0218b3d16ed662d9bcd4 766583abd69fcf242e3ff1f6c562ea5e a0a6c098484a9bb70f0242844188f52d f98c8ccce8bb938fb325d779d7b971c6 5d49531a71b940ca4958485e9fee72f1 x86-64 Platform: openSUSE 10.2: 23591c785aaef10d3b422eebebbb1499 f090dfa3c21f4071ac7312bfa0c76512 9af61b7d487a6025107dfabf76b1d307 d8b8ff18dfe16e6b8a4e7eea39b46fdc 46d10714bd4534d578564b521cc4e5ee 3352eb7cae2644d12b2761d4280f6a31 8dcb7cd3e271a1a0bcbe843269ee8b52 be734ae165180a801f35d26811a5a5c4 d958bf9cdae6c32bb1e1c36df74fc9fb c9429b316e6eecb6ddc2682d01e170dc 67567fd44fc1b7f3589ad48f31dd87ad 3b95cb4747ac42848e2daf543622770c 97fbb5843ff11f35edc5c54338d0ceb9 46d10243690c90812ced6b1a9d5aa041 0cfe47db6079f91b99f6fea86696d019 34e0a3027a6db5adb8a10560467a651e 6fbe5c405768ae26f9c00b9e6a353352 SUSE LINUX 10.1: 2019045021a97b167ea99ac0c046b101 4889570b65d8eed1283146d1adbef2c5 3b3337acb365adeb2cdd167dc8ab11c3 54d0899c5591c4b546a4328aa023e455 d61a5d6b3ad1418ae8828c632c38753f 043514968a409980de9c26bb326bcf61 79d4a0e1a3ee4ead9c32f2f2a994a3dd b094e7fc68ac93c8cea50dd8c9c9f8fa 57eca0584754764c9676f64a99318eda 2a3bf582c8bf3b3f0e3b659b5a69fa8f e7df071bb25de0dadd8d91d1266e813b ccb9cf8b02a3684bc523b1c8deafa132 e002218ccb079ab3b98c10c6a98e6632 b8d6933ae2cd19aae0333385c6df7179 7d0b549bd3ff3e55363dce19060797e1 f904919d8bb75ca477a580dc5483209d 4c3d083e708e17e0747e98d605cf2445 acfe0ccbdf408e2800b2410b7f7f38b6 Sources: openSUSE 10.2: 4d7e3741dccd7caa42bdc630dfe258fa 4165d9c7bfe3e9fe270a881a152d280a SUSE LINUX 10.1: 24e736054c58c12f64133037a8cf2f10 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: SUSE SLES 10 http://support.novell.com/techcenter/psdb/42c27df99955c5253c97cbbfb7b56d6f.html SLE SDK 10 http://support.novell.com/techcenter/psdb/42c27df99955c5253c97cbbfb7b56d6f.html SUSE SLED 10 http://support.novell.com/techcenter/psdb/42c27df99955c5253c97cbbfb7b56d6f.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. ====================================================================

Get the Latest News & Insights