November 2002 - openSUSE Security - openSUSE Mailing Lists

SuSE 8.0 compromises WLan security
by Mathias Homann 18 Nov '02

18 Nov '02

Hi, what I have: - Tekram AP104 802.11b base - Elsa AirLancer MC-11 Trouble: I have to set thet access point to broadcast its SSID and accept stations with their own SSID set to unspecified or SuSE can't connect to it... Hints? bye, MH -- Die unaufgeforderte Zusendung einer Werbemail an Privatleute verstößt gegen §1 UWG und §823 I BGB (Beschluß des LG Berlin vom 2.8.1998 Az: 16 O 201/98). Jede kommerzielle Nutzung der übermittelten persönlichen Daten sowie deren Weitergabe an Dritte ist ausdrücklich untersagt!

2 3

which users
by Piet Roorda 18 Nov '02

18 Nov '02

suse 7.3 I got a unfamiliar mail for localhost: what is the best way to check which users are logged on? piet

2 1

SuSE Security Announcement: SuSE-SA:2002:043 (traceroute-nanog/nkitb)
by Thomas Biege 18 Nov '02

18 Nov '02

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: traceroute-nanog/nkitb Announcement-ID: SuSE-SA:2002:043 Date: Tuesday, Nov 12th 2002 09:30 MEST Affected products: 7.0, 7.1, 7.2, 7.3, 8.0 SuSE eMail Server 3.1 SuSE eMail Server III SuSE Firewall Adminhost VPN SuSE Linux Admin-CD for Firewall SuSE Firewall on CD 2 - VPN SuSE Firewall on CD 2 SuSE Linux Connectivity Server SuSE Linux Enterprise Server 7 SuSE Linux Office Server Vulnerability Type: local root Severity (1-10): 4 SuSE default package: yes Cross References: none Content of this advisory: 1) security vulnerability resolved: - dropping root after gaining raw socket - a few buffer overflows 2) pending vulnerabilities, solutions, workarounds: - ypserv - horde - openssh - wrong MD5 sums in advisory SuSE-SA:2002:041 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Traceroute is a tool that can be used to track packets in a TCP/IP network to determine it's route or to find out about not working routers. Traceroute-nanog requires root privilege to open a raw socket. It does not relinquish these privileges after doing so. This allows a malicious user to gain root access by exploiting a buffer overflow at a later point. For all products prior to 8.1, the traceroute package contains the NANOG implementation. This package is installed by default. Starting with 8.1, SuSE Linux contains a traceroute program rewritten by Olaf Kirch that does not require root privileges anymore. This version of traceroute is not vulnerable. This is the first update for the traceroute package on the SuSE Linux distributions 7.1 through 8.0. We have changed the version string in the update packages to read "6.x" instead of the former "nanog_6.x" to enable a clean comparison between version numbers. This change is misleading in that it suggests that the package name has been changed. Since only the version string is affected, the name of the package remains the same. As a workaround you can remove the setuid bit or just allow trusted users to execute traceroute-nanog. Become root and add the following line to /etc/permissions.local: "/usr/sbin/traceroute root.trusted 4750" This line will keep the setuid root bit for /usr/sbin/traceroute and just allow users in group trusted to execute the binary. To make the permission change and keep it permanent you have to run chkstat(8): "chkstat -set /etc/permissions.local" Please download the update package for your distribution and verify its integrity by the methods listed in section 3) of this announcement. Then, install the package using the command "rpm -Fhv file.rpm" to apply the update. Our maintenance customers are being notified individually. The packages are being offered to install from the maintenance web. Missing packages are being built and tested and will be available for download soon. Intel i386 Platform: SuSE-8.0: ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/traceroute-6.1.1-0.i386.rpm afe01bf0b151eca2f42fa5737c99bdc7 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/traceroute-6.1.1-0.src.rpm ee35e7cf554daa37a3976f473d4192f1 SuSE-7.3: ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/traceroute-6.1.1-0.i386.rpm 0ef0c0153532fcefdf776311503e590b source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/traceroute-6.1.1-0.src.rpm 15a9f3dba6339f0a0bb57ce17d2d9894 SuSE-7.2: ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/traceroute-6.1.1-0.i386.rpm 3b9acb72a3208e3e4e92c0df8ab8d46f source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/traceroute-6.1.1-0.src.rpm a6fd1c7dc3bea4d08ef1efdcbc30fff6 SuSE-7.1: ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/traceroute-6.0-0.i386.rpm 1ac8de3a6e54451bae8e3068f2fbd1e9 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/traceroute-6.0-0.src.rpm 291036123b377184fdf0231d6878f57d SuSE-7.0: ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/nkitb-2002.11.6-0.i386.rpm b1105bc6916a5fdbd54db63d52ec3d81 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/nkitb-2002.11.6-0.src.rpm 3061bd5e551995d62c96da133927a612 Sparc Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/traceroute-6.1.1-0.sparc.rpm 638b868bedab639292d740e60cd0b266 source rpm(s): ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/traceroute-6.1.1-0.src.rpm 10a996ae6a2b4b739bca8f5e9d65e2da AXP Alpha Platform: SuSE-7.1: ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/traceroute-6.0-0.alpha.rpm f2d241cd2331bb3de3382b338fba50b8 source rpm(s): ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/traceroute-6.0-0.src.rpm 949737f63fe99b4476b9c325bdc966fc SuSE-7.0: ftp://ftp.suse.com/pub/suse/axp/update/7.0/a1/nkitb-2002.11.6-0.alpha.rpm 04a5746b70af2e99f8a31b86e16cb470 source rpm(s): ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/nkitb-2002.11.6-0.src.rpm 83abbae6c15ee25adc702047d41a6564 PPC Power PC Platform: SuSE-7.3: ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/traceroute-6.1.1-0.ppc.rpm a00ed346efdc8992b6cf92b890dcc7db source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/traceroute-6.1.1-0.src.rpm 8bfd655104212afc745ea998f0fe6d84 SuSE-7.1: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/traceroute-6.0-0.ppc.rpm 0dc4fa991f1b6a2260af694b9b73ff1a source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/traceroute-6.0-0.src.rpm 9e60c951a66e635cab2aa46559f4aa4e SuSE-7.0: ftp://ftp.suse.com/pub/suse/ppc/update/7.0/a1/nkitb-2002.11.6-0.ppc.rpm eb7d62c5e6ae971a6a96d8a475b8d9fb source rpm(s): ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/nkitb-2002.11.6-0.src.rpm c4b5a31e58a91b5dbd0b6ba497e69046 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - horde There was a cross-site scripting vulnerability in horde. Updated packages have been released for 7.3, 8.0 and 8.1. - openssh When the SSH daemon finds that a user's password has expired, the user is forced to set a new password. While doing so, sshd did not turn off the terminal echo, causing the password to be visible on the screen as it was typed. We are in the process of releasing updated package for 7.0 through 7.3. SuSE Linux 8.0 and 8.1 are not affected. - ypserv Thorsten Kukuk found a memory leak in ypserv that caused it to lose small amounts of memory each time it processes certain malformed requests. This could be used by an attacker to kill ypserv by repeating this exercise until it runs out of memory. We have released updated packages for 7.0 through 8.0. SuSE Linux 8.1 is not affected. - wrong MD5 sums in advisory SuSE-SA:2002:041 Due to a mistake the SuSE Security Announcement SuSE-SA:2002:041 (perl-Mailtools) contains wrong MD5 sums. A new version will be published on our security web sites soon. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. 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) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> 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 announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de) the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an un-installed rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the top-level directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security announcements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. ===================================================================== SuSE's security contact is <security(a)suse.com> or <security(a)suse.de>. The <security(a)suse.de> public key is listed below. ===================================================================== ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the clear-text signature shows proof of the authenticity of the text. SuSE Linux AG makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff 4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3 0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot 1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/ HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM 523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q 2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8 QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ 1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1 wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol 0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J /LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8 RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ 8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X 11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA 8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+ AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0 zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM /3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7 whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE= =LRKC - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBPdD1JHey5gA9JdPZAQFk9gf9G4vs4m1GH5VdDOBGnS6E/ElvnD+IgMRH Im/TbR7CXisww90x254rs1keMRoZFPyb87loDhSPXe1wl9hCDWYiYRZk8YtkeKYw PucnESkJvtzhIu8WeiJY4eENsRbk8776OKDSnYUbZ4XiWI5Dh4uJnRtZT6XF/tDQ 0cdi5JTMc8pmRSnxlzBSO8LxSF5/gS8MKNb2QPHCxGoLf+xn4Z+VpSxNOCXIRmhy nCyEIUkUvtpuKN159KSyyBzQQbZcHsWXdNqoySWR+NVVzY6fmfWUYtqaGar3F0Nd 3QxiBPckpF5zook4cLIPBe0Hrtwvi11ZCTySwbTDIYaM4NEv2Ha7NQ== =X5pd -----END PGP SIGNATURE----- Bye, Thomas -- Thomas Biege <thomas(a)suse.de> SuSE Linux AG,Deutschherrnstr. 15-19,90429 Nuernberg Function: Security Support & Auditing "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka" Key fingerprint = 51 AD B9 C7 34 FC F2 54 01 4A 1C D4 66 64 09 83 -- Cold silence has a tendency to atrophy any sense of compassion - Maynard James Keenan

3 3

Yast YOU bugs
by Hemsley, Trevor 18 Nov '02

18 Nov '02

Hi SuSE people Is it possible that you could either supply a fixed version of YOU or, alternatively and possibly better, open source it so that some of us can fix the bugs in it. It's now becoming almost impossible to use and practically amounts to a denial of service attack on a SuSE 7.1 machine on which it's run. It contains massive memory leaks and currently, with the number of patch description files available for 7.1 on the SuSE ftp site, it now allocates over 300MB RAM and then blows up if there isn't enough swap space available to handle this. For those of us with 64MB or 128MB machines it takes so long to run YOU that it's getting ridiculous. If you use ftp.suse.com as a source then by the time it's got the patch list downloaded, it's timed the ftp session out and it doesn't have any error recovery from this situation and you have to start all over again... and that's on a machine with 896MB RAM so it doesn't even hit swap at all! I've also used it on 7.3 and it doesn't appear to be much better there either. On 8.0 it isn't quite as bloated so perhaps a backport of the fixes to 7.1/7.3 could be possible? I'd be quite willing to fix the memory leaks if you'd care to make the source available to me. Just 'cos it's called y2bignfat doesn't mean it should be ;-) And, yes, I'm aware of fou4s but I'm of the opinion that if a vendor supplies a tool with which to patch their distributions then it should actually work reliably! This isn't intended to be a flame BTW, just in case it sounds like one! Trevor

4 3

allow VPN (pp2p) through firewall
by Patrick Ofner 18 Nov '02

18 Nov '02

Hi, I want to connect two windows boxes through a vpn (pp2p), but between them there is a Linux firewall (kernel 2.2.18 , ipchains). What rules must i create?

2 1

WG: [RHSA-2002:262-07] New kernel fixes local denial of service issue
by Christoph Illnar 18 Nov '02

18 Nov '02

Hello SuSE-Security Team! Is there any bugfix for SuSE-kernels in progress? We encountered such a behavior in the wild, because one of our servers freezed 2 times within the last week. but is it possible to attack it without having local access permissions? upgrading to a newer kernel version unfortunately is not an option because of the promise fasttrack raid... :-( thank you for your great work! greets, Christoph Illnar > -----Ursprüngliche Nachricht----- > Von: bugzilla(a)redhat.com [mailto:bugzilla@redhat.com] > Gesendet: Samstag, 16. November 2002 12:07 > An: redhat-watch-list(a)redhat.com; redhat-announce-list(a)redhat.com > Betreff: [RHSA-2002:262-07] New kernel fixes local denial of service > issue > > > --------------------------------------------------------------------- > Red Hat, Inc. Red Hat Security Advisory > > Synopsis: New kernel fixes local denial of service issue > Advisory ID: RHSA-2002:262-07 > Issue date: 2002-09-23 > Updated on: 2002-11-16 > Product: Red Hat Linux > Keywords: bugtraq DoS > Cross references: > Obsoletes: RHSA-2002:205 RHSA-2002:206 > --------------------------------------------------------------------- > > 1. Topic: > > The kernel in Red Hat Linux 7.1, 7.1K, 7.2, 7.3, and 8.0 are vulnerable to > a local denial of service attack. Updated packages are available which > address this vulnerability, as well as bugs in several drivers. > > 2. Relevant releases/architectures: > > Red Hat Linux 7.1 - athlon, i386, i586, i686 > Red Hat Linux 7.2 - athlon, i386, i586, i686 > Red Hat Linux 7.3 - athlon, i386, i586, i686 > Red Hat Linux 8.0 - athlon, i386, i586, i686 > > 3. Problem description: > > The Linux kernel handles the basic functions of the operating system. > A vulnerability in the Linux kernel has been discovered in which > a non-root > user can cause the machine to freeze. This kernel addresses the > vulnerability. > > Note: This bug is specific to the x86 architecture kernels only, and does > not affect ia64 or other architectures. > > In addition, a bug in the maestro3 soundcard driver has been fixed as well > as a bug in the xircom pcmcia driver network driver and the tg3 network > driver for Broadcom gigabit ethernet chips. > > All users of Red Hat Linux 7.1, 7.1K, 7.2, 7.3, and 8.0 should upgrade to > these errata packages, which are not vulnerable to this issue. > > Thanks go to Christopher Devine for reporting the vulnerability > on bugtraq, > and Petr Vandrovec for being the first to supply a fix to the community. > > 4. Solution: > > Before applying this update, make sure all previously released errata > relevant to your system have been applied, especially the additional > packages from RHSA-2002:205 and RHSA-2002:206 respectively. > > The procedure for upgrading the kernel manually is documented at: > > http://www.redhat.com/support/docs/howto/kernel-upgrade/ > > Please read the directions for your architecture carefully before > proceeding with the kernel upgrade. > > Please note that this update is also available via Red Hat Network. Many > people find this to be an easier way to apply updates. To use Red Hat > Network, launch the Red Hat Update Agent with the following command: > > up2date > > This will start an interactive process that will result in the appropriate > RPMs being upgraded on your system. Note that you need to select > the kernel > explicitly on default configurations of up2date. > > 5. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla for more info): > > 77834 - Working Dos from bugtraq mailing list > 69920 - Kernel Crashes in TG3 Driver > 76171 - kernel-2.4.18-17.7.x update caused maestro3 to stop working > 77138 - Sound Modules Fail for Enigma kernel 2.4.18-17.7.x on > Dell Latitude J750 > 76555 - problems with kernel-2.4.18-17.8.0 on Dell Latitude CPx > 77565 - [gdth] NULL pointer dereference in scsi.c > (scsi_release_commandblocks) > 76233 - new kernel up2date hangs laptop at shutdown > 77241 - esd peaks CPU w/ kernel 2.4.18-17.8.0 on Dell Inspiron 8100 > 77258 - Ethernet interface not working on SiS 963 south bridge > (SiS 648 chipset) > 77134 - Sound Modules fail for Enigma kernel 2.4.18-17.7.x > 76385 - 2.4.18-17.7.x update breaks Wacom tablet support > 75359 - kernel source does not compile due to missing include files > 76624 - Segmentation Fault using GDTH on RH72 kernel-smp-2.4.18-17.7.x > 76206 - xirc2ps_cs hangs apmd after upgrading to 2.4.18-17 > > 6. RPMs required: > > Red Hat Linux 7.1: > > SRPMS: > ftp://updates.redhat.com/7.1/en/os/SRPMS/kernel-2.4.18-18.7.x.src.rpm > > athlon: > ftp://updates.redhat.com/7.1/en/os/athlon/kernel-2.4.18-18.7.x.athlon.rpm > ftp://updates.redhat.com/7.1/en/os/athlon/kernel-smp-2.4.18-18.7.x > .athlon.rpm > > i386: > ftp://updates.redhat.com/7.1/en/os/i386/kernel-2.4.18-18.7.x.i386.rpm > ftp://updates.redhat.com/7.1/en/os/i386/kernel-source-2.4.18-18.7. > x.i386.rpm > ftp://updates.redhat.com/7.1/en/os/i386/kernel-doc-2.4.18-18.7.x.i386.rpm > ftp://updates.redhat.com/7.1/en/os/i386/kernel-BOOT-2.4.18-18.7.x.i386.rpm > > i586: > ftp://updates.redhat.com/7.1/en/os/i586/kernel-2.4.18-18.7.x.i586.rpm > ftp://updates.redhat.com/7.1/en/os/i586/kernel-smp-2.4.18-18.7.x.i586.rpm > > i686: > ftp://updates.redhat.com/7.1/en/os/i686/kernel-2.4.18-18.7.x.i686.rpm > ftp://updates.redhat.com/7.1/en/os/i686/kernel-smp-2.4.18-18.7.x.i686.rpm > ftp://updates.redhat.com/7.1/en/os/i686/kernel-bigmem-2.4.18-18.7. > x.i686.rpm > ftp://updates.redhat.com/7.1/en/os/i686/kernel-debug-2.4.18-18.7.x > .i686.rpm > > Red Hat Linux 7.2: > > SRPMS: > ftp://updates.redhat.com/7.2/en/os/SRPMS/kernel-2.4.18-18.7.x.src.rpm > > athlon: > ftp://updates.redhat.com/7.2/en/os/athlon/kernel-2.4.18-18.7.x.athlon.rpm > ftp://updates.redhat.com/7.2/en/os/athlon/kernel-smp-2.4.18-18.7.x > .athlon.rpm > > i386: > ftp://updates.redhat.com/7.2/en/os/i386/kernel-2.4.18-18.7.x.i386.rpm > ftp://updates.redhat.com/7.2/en/os/i386/kernel-source-2.4.18-18.7. > x.i386.rpm > ftp://updates.redhat.com/7.2/en/os/i386/kernel-doc-2.4.18-18.7.x.i386.rpm > ftp://updates.redhat.com/7.2/en/os/i386/kernel-BOOT-2.4.18-18.7.x.i386.rpm > > i586: > ftp://updates.redhat.com/7.2/en/os/i586/kernel-2.4.18-18.7.x.i586.rpm > ftp://updates.redhat.com/7.2/en/os/i586/kernel-smp-2.4.18-18.7.x.i586.rpm > > i686: > ftp://updates.redhat.com/7.2/en/os/i686/kernel-2.4.18-18.7.x.i686.rpm > ftp://updates.redhat.com/7.2/en/os/i686/kernel-smp-2.4.18-18.7.x.i686.rpm > ftp://updates.redhat.com/7.2/en/os/i686/kernel-bigmem-2.4.18-18.7. > x.i686.rpm > ftp://updates.redhat.com/7.2/en/os/i686/kernel-debug-2.4.18-18.7.x > .i686.rpm > > Red Hat Linux 7.3: > > SRPMS: > ftp://updates.redhat.com/7.3/en/os/SRPMS/kernel-2.4.18-18.7.x.src.rpm > > athlon: > ftp://updates.redhat.com/7.3/en/os/athlon/kernel-2.4.18-18.7.x.athlon.rpm > ftp://updates.redhat.com/7.3/en/os/athlon/kernel-smp-2.4.18-18.7.x > .athlon.rpm > > i386: > ftp://updates.redhat.com/7.3/en/os/i386/kernel-2.4.18-18.7.x.i386.rpm > ftp://updates.redhat.com/7.3/en/os/i386/kernel-source-2.4.18-18.7. > x.i386.rpm > ftp://updates.redhat.com/7.3/en/os/i386/kernel-doc-2.4.18-18.7.x.i386.rpm > ftp://updates.redhat.com/7.3/en/os/i386/kernel-BOOT-2.4.18-18.7.x.i386.rpm > > i586: > ftp://updates.redhat.com/7.3/en/os/i586/kernel-2.4.18-18.7.x.i586.rpm > ftp://updates.redhat.com/7.3/en/os/i586/kernel-smp-2.4.18-18.7.x.i586.rpm > > i686: > ftp://updates.redhat.com/7.3/en/os/i686/kernel-2.4.18-18.7.x.i686.rpm > ftp://updates.redhat.com/7.3/en/os/i686/kernel-smp-2.4.18-18.7.x.i686.rpm > ftp://updates.redhat.com/7.3/en/os/i686/kernel-bigmem-2.4.18-18.7. > x.i686.rpm > ftp://updates.redhat.com/7.3/en/os/i686/kernel-debug-2.4.18-18.7.x > .i686.rpm > > Red Hat Linux 8.0: > > SRPMS: > ftp://updates.redhat.com/8.0/en/os/SRPMS/kernel-2.4.18-18.8.0.src.rpm > > athlon: > ftp://updates.redhat.com/8.0/en/os/athlon/kernel-2.4.18-18.8.0.athlon.rpm > ftp://updates.redhat.com/8.0/en/os/athlon/kernel-smp-2.4.18-18.8.0 > .athlon.rpm > > i386: > ftp://updates.redhat.com/8.0/en/os/i386/kernel-2.4.18-18.8.0.i386.rpm > ftp://updates.redhat.com/8.0/en/os/i386/kernel-source-2.4.18-18.8. > 0.i386.rpm > ftp://updates.redhat.com/8.0/en/os/i386/kernel-doc-2.4.18-18.8.0.i386.rpm > ftp://updates.redhat.com/8.0/en/os/i386/kernel-BOOT-2.4.18-18.8.0.i386.rpm > > i586: > ftp://updates.redhat.com/8.0/en/os/i586/kernel-2.4.18-18.8.0.i586.rpm > ftp://updates.redhat.com/8.0/en/os/i586/kernel-smp-2.4.18-18.8.0.i586.rpm > > i686: > ftp://updates.redhat.com/8.0/en/os/i686/kernel-2.4.18-18.8.0.i686.rpm > ftp://updates.redhat.com/8.0/en/os/i686/kernel-smp-2.4.18-18.8.0.i686.rpm > ftp://updates.redhat.com/8.0/en/os/i686/kernel-bigmem-2.4.18-18.8. > 0.i686.rpm > ftp://updates.redhat.com/8.0/en/os/i686/kernel-debug-2.4.18-18.8.0 > .i686.rpm > ftp://updates.redhat.com/8.0/en/os/i686/kernel-uml-2.4.18-18.8.0.i686.rpm > > > > 7. Verification: > > MD5 sum Package Name > -------------------------------------------------------------------------- > 7f8581e632826cafd7530109c79c19bb > 7.1/en/os/SRPMS/kernel-2.4.18-18.7.x.src.rpm > e38b754b71fb5a091f3bce785c968724 > 7.1/en/os/athlon/kernel-2.4.18-18.7.x.athlon.rpm > 0ab8f1aa236289f6c3c9c152cd578669 > 7.1/en/os/athlon/kernel-smp-2.4.18-18.7.x.athlon.rpm > d16d76b77189d9da17481e9c0e0cc0ca > 7.1/en/os/i386/kernel-2.4.18-18.7.x.i386.rpm > 026e9c4a13ba2fd3fdd49eb9b2f432ea > 7.1/en/os/i386/kernel-BOOT-2.4.18-18.7.x.i386.rpm > 02c6831a3e971fab22ecbb5f1e1a09f3 > 7.1/en/os/i386/kernel-doc-2.4.18-18.7.x.i386.rpm > a81a5af709b40d713100a82124e7c0dd > 7.1/en/os/i386/kernel-source-2.4.18-18.7.x.i386.rpm > fd20bdd2a82510eab8e8498fec0232fb > 7.1/en/os/i586/kernel-2.4.18-18.7.x.i586.rpm > a1ed7b8fd3d6de8db0ec73b0b4e75f1d > 7.1/en/os/i586/kernel-smp-2.4.18-18.7.x.i586.rpm > d8adfe12ad67f8bac27339a450b97499 > 7.1/en/os/i686/kernel-2.4.18-18.7.x.i686.rpm > ff7a46200b12e53e5092b9d889c7cb9c > 7.1/en/os/i686/kernel-bigmem-2.4.18-18.7.x.i686.rpm > 61e83bb1999b8fa861fb98f41b8f46ef > 7.1/en/os/i686/kernel-debug-2.4.18-18.7.x.i686.rpm > 20be5fba2e3ebe73c1126bb61fce6c43 > 7.1/en/os/i686/kernel-smp-2.4.18-18.7.x.i686.rpm > 7f8581e632826cafd7530109c79c19bb > 7.2/en/os/SRPMS/kernel-2.4.18-18.7.x.src.rpm > e38b754b71fb5a091f3bce785c968724 > 7.2/en/os/athlon/kernel-2.4.18-18.7.x.athlon.rpm > 0ab8f1aa236289f6c3c9c152cd578669 > 7.2/en/os/athlon/kernel-smp-2.4.18-18.7.x.athlon.rpm > d16d76b77189d9da17481e9c0e0cc0ca > 7.2/en/os/i386/kernel-2.4.18-18.7.x.i386.rpm > 026e9c4a13ba2fd3fdd49eb9b2f432ea > 7.2/en/os/i386/kernel-BOOT-2.4.18-18.7.x.i386.rpm > 02c6831a3e971fab22ecbb5f1e1a09f3 > 7.2/en/os/i386/kernel-doc-2.4.18-18.7.x.i386.rpm > a81a5af709b40d713100a82124e7c0dd > 7.2/en/os/i386/kernel-source-2.4.18-18.7.x.i386.rpm > fd20bdd2a82510eab8e8498fec0232fb > 7.2/en/os/i586/kernel-2.4.18-18.7.x.i586.rpm > a1ed7b8fd3d6de8db0ec73b0b4e75f1d > 7.2/en/os/i586/kernel-smp-2.4.18-18.7.x.i586.rpm > d8adfe12ad67f8bac27339a450b97499 > 7.2/en/os/i686/kernel-2.4.18-18.7.x.i686.rpm > ff7a46200b12e53e5092b9d889c7cb9c > 7.2/en/os/i686/kernel-bigmem-2.4.18-18.7.x.i686.rpm > 61e83bb1999b8fa861fb98f41b8f46ef > 7.2/en/os/i686/kernel-debug-2.4.18-18.7.x.i686.rpm > 20be5fba2e3ebe73c1126bb61fce6c43 > 7.2/en/os/i686/kernel-smp-2.4.18-18.7.x.i686.rpm > 7f8581e632826cafd7530109c79c19bb > 7.3/en/os/SRPMS/kernel-2.4.18-18.7.x.src.rpm > e38b754b71fb5a091f3bce785c968724 > 7.3/en/os/athlon/kernel-2.4.18-18.7.x.athlon.rpm > 0ab8f1aa236289f6c3c9c152cd578669 > 7.3/en/os/athlon/kernel-smp-2.4.18-18.7.x.athlon.rpm > d16d76b77189d9da17481e9c0e0cc0ca > 7.3/en/os/i386/kernel-2.4.18-18.7.x.i386.rpm > 026e9c4a13ba2fd3fdd49eb9b2f432ea > 7.3/en/os/i386/kernel-BOOT-2.4.18-18.7.x.i386.rpm > 02c6831a3e971fab22ecbb5f1e1a09f3 > 7.3/en/os/i386/kernel-doc-2.4.18-18.7.x.i386.rpm > a81a5af709b40d713100a82124e7c0dd > 7.3/en/os/i386/kernel-source-2.4.18-18.7.x.i386.rpm > fd20bdd2a82510eab8e8498fec0232fb > 7.3/en/os/i586/kernel-2.4.18-18.7.x.i586.rpm > a1ed7b8fd3d6de8db0ec73b0b4e75f1d > 7.3/en/os/i586/kernel-smp-2.4.18-18.7.x.i586.rpm > d8adfe12ad67f8bac27339a450b97499 > 7.3/en/os/i686/kernel-2.4.18-18.7.x.i686.rpm > ff7a46200b12e53e5092b9d889c7cb9c > 7.3/en/os/i686/kernel-bigmem-2.4.18-18.7.x.i686.rpm > 61e83bb1999b8fa861fb98f41b8f46ef > 7.3/en/os/i686/kernel-debug-2.4.18-18.7.x.i686.rpm > 20be5fba2e3ebe73c1126bb61fce6c43 > 7.3/en/os/i686/kernel-smp-2.4.18-18.7.x.i686.rpm > 65f6590b550c8a0d0b04bb885c12368d > 8.0/en/os/SRPMS/kernel-2.4.18-18.8.0.src.rpm > 946a8573a7af951a37f91bfbd445da07 > 8.0/en/os/athlon/kernel-2.4.18-18.8.0.athlon.rpm > c31721f77fc44fd6bab38c75ff66fa17 > 8.0/en/os/athlon/kernel-smp-2.4.18-18.8.0.athlon.rpm > 6da80288107c7b7bb574c8aa47242e3b > 8.0/en/os/i386/kernel-2.4.18-18.8.0.i386.rpm > 889397ada127361d19bb29c83eb33b57 > 8.0/en/os/i386/kernel-BOOT-2.4.18-18.8.0.i386.rpm > 9c91e050657805d547b1664ca55d7691 > 8.0/en/os/i386/kernel-doc-2.4.18-18.8.0.i386.rpm > b99ffefa103eeb4d12ad6efae9cf4ef1 > 8.0/en/os/i386/kernel-source-2.4.18-18.8.0.i386.rpm > 93835d95e05a593fd86b497259d6a313 > 8.0/en/os/i586/kernel-2.4.18-18.8.0.i586.rpm > 6ba903e2c94ea619baf10ebffdfd9a15 > 8.0/en/os/i586/kernel-smp-2.4.18-18.8.0.i586.rpm > 41fea4a230a8989d16151fe21b38c9d4 > 8.0/en/os/i686/kernel-2.4.18-18.8.0.i686.rpm > 3b5aa2480f92f79b2a9f597a865dc6a5 > 8.0/en/os/i686/kernel-bigmem-2.4.18-18.8.0.i686.rpm > 6026588279d9871ffac63e15a9091563 > 8.0/en/os/i686/kernel-debug-2.4.18-18.8.0.i686.rpm > b94e4989c4c28fab3fbe1fa8b79ea902 > 8.0/en/os/i686/kernel-smp-2.4.18-18.8.0.i686.rpm > be0e87f588f1995d48ed72c3251d21be > 8.0/en/os/i686/kernel-uml-2.4.18-18.8.0.i686.rpm > > > These packages are GPG signed by Red Hat, Inc. for security. Our key > is available at http://www.redhat.com/about/contact/pgpkey.html > > You can verify each package with the following command: > > rpm --checksig -v <filename> > > If you only wish to verify that each package has not been corrupted or > tampered with, examine only the md5sum with the following command: > > md5sum <filename> > > > 8. References: > > http://online.securityfocus.com/archive/1/299687/2002-11-11/2002-11-17/0 > > 9. Contact: > > The Red Hat security contact is <security(a)redhat.com>. More contact > details at http://www.redhat.com/solutions/security/news/contact.html > > Copyright(c) 2000, 2001, 2002 Red Hat, Inc.

1 0

what's the benifit of the EA(extended attribute)?
by Wade(Huide) Yin 18 Nov '02

18 Nov '02

which one is better between the EA and LSM... I think the scalability of LSM is good, but how about EA ? Who can give an opinion on this topic ... Best Regards Wade

1 0

port 3349
by Piet Roorda 17 Nov '02

17 Nov '02

what is on port 3349 and why is it scanned? regards,piet Nov 17 13:00:21 photoserver kernel: SuSE-FW-DROP-DEFAULTIN=ppp0 OUT= MAC= SRC=213.84.37.226 DST=213.17.44.160 LEN=64 TOS=0x00 PREC=0x00 TTL=55 ID=14625 DF PROTO=TCP SPT=1210 DPT=3349 WINDOW=64240 RES=0x00 SYN URGP=0 OPT (02040584010303000101080A000000000000000001010402) Nov 17 13:02:43 photoserver kernel: SuSE-FW-DROP-DEFAULTIN=ppp0 OUT= MAC= SRC=213.84.37.226 DST=213.17.44.160 LEN=64 TOS=0x00 PREC=0x00 TTL=55 ID=16716 DF PROTO=TCP SPT=1268 DPT=3349 WINDOW=64240 RES=0x00 SYN URGP=0 OPT (02040584010303000101080A000000000000000001010402) Nov 17 13:02:46 photoserver kernel: SuSE-FW-DROP-DEFAULTIN=ppp0 OUT= MAC= SRC=213.84.37.226 DST=213.17.44.160 LEN=64 TOS=0x00 PREC=0x00 TTL=55 ID=16761 DF PROTO=TCP SPT=1268 DPT=3349 WINDOW=64240 RES=0x00 SYN URGP=0 OPT (02040584010303000101080A000000000000000001010402) Nov 17 13:02:52 photoserver kernel: SuSE-FW-DROP-DEFAULTIN=ppp0 OUT= MAC= SRC=213.84.37.226 DST=213.17.44.160 LEN=64 TOS=0x00 PREC=0x00 TTL=55 ID=16822 DF PROTO=TCP SPT=1268 DPT=3349 WINDOW=64240 RES=0x00 SYN URGP=0 OPT (02040584010303000101080A000000000000000001010402) Nov 17 13:08:34 photoserver kernel: SuSE-FW-DROP-DEFAULTIN=ppp0 OUT= MAC= SRC=213.229.69.85 DST=213.17.44.160 LEN=78 TOS=0x00 PREC=0x00 TTL=119 ID=62847 PROTO=UDP SPT=1025 DPT=137 LEN=58 Nov 17 13:09:24 photoserver kernel: SuSE-FW-DROP-DEFAULTIN=ppp0 OUT= MAC= SRC=217.165.78.180 DST=213.17.44.160 LEN=78 TOS=0x00 PREC=0x00 TTL=112 ID=44132 PROTO=UDP SPT=13326 DPT=137 LEN=58

2 1

SW2 on 8.1 blocks dialed-in computer
by Helge Jung (ECO-Logic) 16 Nov '02

16 Nov '02

Hi list, I think this will be an easy question for you: I've DSL set up on eth1/ppp0 and my LAN connected on eth0 - SuSEfirewall2 (SuSE Linux 8.1) is running. Routing/NAT is enabled and everything's working fine (I didn't touched the settings in the config file, I used only YaST). I've configured my linux pc as a isdn-dialin-server and the dialin is working just fine except that as long as the firewall is activated I can't ping the pc which dialed in and pinging from the other way round isn't possible, too - nor is any other kind of network communication (SSH, HTTP, etc.). The firewall seems to block the dialed in computer (ippp0). Which settings do I have to set up that when a other PC dials in it can access at least my linux pc over SSH (Port 22) and HTTP (80). Best regards and thanks in advance, Helge Jung

2 2

kdelibs3 security update
by Lars Ellenberg 15 Nov '02

15 Nov '02

if you happen to have the kdelibs3-devel rpm installed, the security update for kdelibs3-3.0.5 refuses to install because -devel needs kdelibs3-3.0.4. so you have to deinstall -devel, or use -nodep; I do not like either. cheers, Lars btw, someone understands why yast does run at all without its core package? this is a recommended patch: # rpm -Uhv autoyast2-installation-2.6.38-1.noarch.patch.rpm error: failed dependencies: yast2-core is needed by autoyast2-installation-2.6.38-1 # rpm -q yast2-core package yast2-core is not installed # rpm -q --whatprovides yast2-core no package provides yast2-core but now, how comes this: # rpm -q --whatrequires yast2-core yast2-pam-2.6.5-7 yast2-2.6.34-3 yast2-backup-2.6.7-25 yast2-restore-2.6.10-25 autoyast2-installation-2.6.35-0 yast2-sound-2.6.23-3 (default installation SuSE 8.1)

1 0