openSUSE Security January 2005

security@lists.opensuse.org

93 participants
61 discussions

SUSE Security Announcement: kernel local privilege escalation (SUSE-SA:2005:003)
by Marcus Meissner 16 Feb '05

16 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement-ID: SUSE-SA:2005:003 Date: Friday, Jan 21st 2005 16:00 MET Affected products: 8.1, 8.2, 9.0, 9.1, 9.2 SUSE Linux Enterprise Server 8, 9 SUSE Linux Desktop 1.0 Novell Linux Desktop 9 Vulnerability Type: local privilege escalation Severity (1-10): 7 SUSE default package: yes Cross References: CAN-2004-1235 CAN-2005-0001 Content of this advisory: 1) security vulnerability resolved: - local privilege escalation - local denial of service attacks problem description 2) solution/workaround 3) special instructions and notes 4) package location and checksums 5) pending vulnerabilities, solutions, workarounds: - see summary report 6) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion Several exploitable security problems were identified and fixed in the Linux kernel, the core of every SUSE Linux product. - Due to missing locking in the sys_uselib system call a local attacker can gain root access. This was found by Paul Starzetz and is tracked by the Mitre CVE ID CAN-2004-1235. - Paul Starzetz also found a race condition in SMP page table handling which could lead to a local attacker gaining root access on SMP machines. This is tracked by the Mitre CVE ID CAN-2005-0001. - A local denial of service was found in the auditing subsystem which have lead a local attacker crashing the machine. This was reported and fixed by Redhat. - The sendmsg / cmsg fix from the previous kernel update was faulty on 64bit systems with 32bit compatibility layer and could lead to 32bit applications not working correctly on those 64bit systems. - The smbfs security fixes from a before-previous kernel update were faulty for some file write cases. - A local denial of service with Direct I/O access to NFS file systems could lead a local attacker to crash a machine with NFS mounts. - grsecurity reported a signed integer problem in the SCSI ioctl handling which had a missing boundary check. Due to C language specifics, this evaluation was not correct and there actually is no problem in this code. The signed / unsigned mismatch was fixed nevertheless. - Several more small non security problems were fixed. NOTE: Two days ago we released the Service Pack 1 for the SUSE Linux Enterprise Server 9. This kernel update contains fixes for the SUSE Linux Enterprise Server 9 GA version kernel line. A fix for the Service Pack 1 version line will be available shortly. 2) solution/workaround There is no workaround. Please install the provided update packages. 3) special instructions and notes SPECIAL INSTALL INSTRUCTIONS: ============================== The following paragraphs will guide you through the installation process in a step-by-step fashion. The character sequence "****" marks the beginning of a new paragraph. In some cases, the steps outlined in a particular paragraph may or may not be applicable to your situation. Therefore, please make sure to read through all of the steps below before attempting any of these procedures. All of the commands that need to be executed are required to be run as the superuser (root). Each step relies on the steps before it to complete successfully. **** Step 1: Determine the needed kernel type Please use the following command to find the kernel type that is installed on your system: rpm -qf /boot/vmlinuz Following are the possible kernel types (disregard the version and build number following the name separated by the "-" character) k_deflt # default kernel, good for most systems. k_i386 # kernel for older processors and chip sets k_athlon # kernel made specifically for AMD Athlon(tm) family processors k_psmp # kernel for Pentium-I dual processor systems k_smp # kernel for SMP systems (Pentium-II and above) k_smp4G # kernel for SMP systems which supports a maximum of 4G of RAM kernel-64k-pagesize kernel-bigsmp kernel-default kernel-smp **** Step 2: Download the package for your system Please download the kernel RPM package for your distribution with the name as indicated by Step 1. The list of all kernel rpm packages is appended below. Note: The kernel-source package does not contain a binary kernel in bootable form. Instead, it contains the sources that the binary kernel rpm packages are created from. It can be used by administrators who have decided to build their own kernel. Since the kernel-source.rpm is an installable (compiled) package that contains sources for the linux kernel, it is not the source RPM for the kernel RPM binary packages. The kernel RPM binary packages for the distributions can be found at the locations below ftp://ftp.suse.com/pub/suse/i386/update/. 8.1/rpm/i586 8.2/rpm/i586 9.0/rpm/i586 9.1/rpm/i586 9.2/rpm/i586 After downloading the kernel RPM package for your system, you should verify the authenticity of the kernel rpm package using the methods as listed in section 3) of each SUSE Security Announcement. **** Step 3: Installing your kernel rpm package Install the rpm package that you have downloaded in Steps 3 or 4 with the command rpm -Uhv --nodeps --force <K_FILE.RPM> where <K_FILE.RPM> is the name of the rpm package that you downloaded. Warning: After performing this step, your system will likely not be able to boot if the following steps have not been fully followed. If you run SUSE LINUX 8.1 and haven't applied the kernel update (SUSE-SA:2003:034), AND you are using the freeswan package, you also need to update the freeswan rpm as a dependency as offered by YOU (YaST Online Update). The package can be downloaded from ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/ **** Step 4: configuring and creating the initrd The initrd is a ramdisk that is loaded into the memory of your system together with the kernel boot image by the bootloader. The kernel uses the content of this ramdisk to execute commands that must be run before the kernel can mount its actual root filesystem. It is usually used to initialize SCSI drivers or NIC drivers for diskless operation. The variable INITRD_MODULES in /etc/sysconfig/kernel determines which kernel modules will be loaded in the initrd before the kernel has mounted its actual root filesystem. The variable should contain your SCSI adapter (if any) or filesystem driver modules. With the installation of the new kernel, the initrd has to be re-packed with the update kernel modules. Please run the command mk_initrd as root to create a new init ramdisk (initrd) for your system. On SuSE Linux 8.1 and later, this is done automatically when the RPM is installed. **** Step 5: bootloader If you run a SUSE LINUX 8.x, SLES8, or SUSE LINUX 9.x system, there are two options: Depending on your software configuration, you have either the lilo bootloader or the grub bootloader installed and initialized on your system. The grub bootloader does not require any further actions to be performed after the new kernel images have been moved in place by the rpm Update command. If you have a lilo bootloader installed and initialized, then the lilo program must be run as root. Use the command grep LOADER_TYPE /etc/sysconfig/bootloader to find out which boot loader is configured. If it is lilo, then you must run the lilo command as root. If grub is listed, then your system does not require any bootloader initialization. Warning: An improperly installed bootloader may render your system unbootable. **** Step 6: reboot If all of the steps above have been successfully completed on your system, then the new kernel including the kernel modules and the initrd should be ready to boot. The system needs to be rebooted for the changes to become active. Please make sure that all steps have completed, then reboot using the command shutdown -r now or init 6 Your system should now shut down and reboot with the new kernel. 4) package location and checksums 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. x86 Platform: SUSE Linux 9.2: ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-source-2.6.8-24… e335f4e401034f79bce9bcef3b6c19e0 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-bigsmp-2.6.8-24… 848b85f02abd3d2877b04f10aa875689 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-smp-2.6.8-24.11… f103cd395e9d6e4418cb8cf91c09147d ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-default-2.6.8-2… 374dc207a2b3e81e04cdad2e3d6c0333 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-um-2.6.8-24.11.… 379085daf7dc1e1df0ce5c246c26caf4 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-source-2.6.8-24.… bbfdc289c2d1f1a73ac6fa759ecfaf87 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-bigsmp-2.6.8-24.… c999bd4ff601c34edc6322fc43caf1a5 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-smp-2.6.8-24.11.… 9539d6093144fbbd066681f61c9aa07d ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-default-2.6.8-24… eeeebf4ea4942f6093b56f7a3d7a7de3 ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-um-2.6.8-24.11.n… 93953b908c54f19d4d30816b4eae2dc9 SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-source-2.6.5-7.… b84574947de5c47a2bcca43525e1fc4d ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-bigsmp-2.6.5-7.… 5346f03accd80530ef1dd870a069dc11 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-smp-2.6.5-7.111… dba08e4e49dbf1f32988152956448ab3 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/kernel-default-2.6.5-7… 231eb3350db6a02b621731790f3b6d37 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-source-2.6.5-7.1… 8cd984fa2f4607ff75b0ff79a82090e0 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-bigsmp-2.6.5-7.1… a64279aae3382a1647f594e59ea321fe ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-smp-2.6.5-7.111.… 653925384a7e887fb59b58a432a86968 ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/kernel-default-2.6.5-7.… f01bbb3541bb8197c36757c9ac554ba9 SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/kernel-source-2.4.21-2… c577564f2588a0f23b2bdf6c53622c88 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-273.i58… e1826b653a6dc121bc09af292469ca60 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_athlon-2.4.21-273.i5… 4f6f2c3181e9ffa3665b078b56263b5f ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp-2.4.21-273.i586.… 93d0f1ac7d07d8965fd995755ced96d8 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp4G-2.4.21-273.i58… dc55afa79f48b332802fcf8c957f4fb1 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_um-2.4.21-273.i586.r… aafbe34c9623ed1558cba1334d9cefb2 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/kernel-source-2.4.21-27… 23d2ec2beb60fe87971679ffcd7aa43b ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_deflt-2.4.21-273.src.… d4570f75c0706913ab28ab591669a09f ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_athlon-2.4.21-273.src… 5c9f06dab451c493ea3805c7c25b5e0e ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp-2.4.21-273.src.rpm 4f9d9932f848a81681d97b2121b95cfc ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp4G-2.4.21-273.src.… 595c9d12751dc3ed7911a0c839aa3798 ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_um-2.4.21-273.src.rpm 3d2030e1fe01309363a62269544d4ecf SUSE Linux 8.2: ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/kernel-source-2.4.20.S… 5929f89029262db0f26f7839cae0144c ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_deflt-2.4.20-129.i58… 1287e9445cf09947056f8330fad24417 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_athlon-2.4.20-129.i5… 9e69c44a2d13d57388272f1991e2c549 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_smp-2.4.20-129.i586.… 345fdb85a6e39f15cd37cecafc8af4c5 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_psmp-2.4.20-129.i586… 0964a18c464c9fd905b8c1efa2cd5ba1 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/kernel-source-2.4.20.Su… 38e1780995f9b8463bb80d8337e9447a ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_deflt-2.4.20-129.src.… 449c13bd8b922c45233df240bb4b02ad ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_athlon-2.4.20-129.src… 05ab0427675e9aba88460e016dbbd601 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_smp-2.4.20-129.src.rpm 86c6b0ae5616e0a72396fb19b3fbf172 ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_psmp-2.4.20-129.src.r… eb488e7c3169936131ff6bac76862fb4 SUSE Linux 8.1: ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/kernel-source-2.4.21-2… d2c2fae409431dc9380b1e230359ed56 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_deflt-2.4.21-273.i58… 503e57660b3b5f6c1eadf60a54e90508 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_athlon-2.4.21-273.i5… 2c5a8cb80db649a50fc64a6a37dd0230 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_smp-2.4.21-273.i586.… 14b2e9a7783986b9293f0561729a5216 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/k_psmp-2.4.21-273.i586… 36930ea9a97e420b67137143bc3fbd06 source rpm(s): ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/kernel-source-2.4.21-27… 70862f0bae01c0003b3cd48c9161c137 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_deflt-2.4.21-273.src.… ef2e870d10237d85d3be66a12371cfe2 ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_athlon-2.4.21-273.src… 87551521c8e569351d47d9c0e097550b ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_smp-2.4.21-273.src.rpm 5062c220dd0ebe012e9f2f71137458ea ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/k_psmp-2.4.21-273.src.r… f6e881395e1d069e2dee910cdb311964 x86-64 Platform: SUSE Linux 9.2: ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-source-2.6.… d8d5dfd431c9b989195f94d3d3c1ea64 ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-smp-2.6.8-2… 3a16e2109a1dbf177500430213e45b69 ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/kernel-default-2.6… 51213878a7116455b9443688d0b39aa0 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-source-2.6.8-2… bbfdc289c2d1f1a73ac6fa759ecfaf87 ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-smp-2.6.8-24.1… 9539d6093144fbbd066681f61c9aa07d ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/kernel-default-2.6.8-… eeeebf4ea4942f6093b56f7a3d7a7de3 SUSE Linux 9.1: ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-source-2.6.… 44996d9e1da1df537cb1b2100553d2af ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-smp-2.6.5-7… 11ad693478569dd691d237679328bd1b ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/kernel-default-2.6… deaeb48a6815587535b1adddf68131ef source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-source-2.6.5-7… fdef7eaed76e07a85ebbba9323b64f8d ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-smp-2.6.5-7.11… 3605a6f50f0d799c73849cb382d786ac ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/kernel-default-2.6.5-… d0410d0e5c32cd44bae3da7b42cac23a SUSE Linux 9.0: ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kernel-source-2.4.… ed6c099957a83fc87abd74e3549e9799 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_deflt-2.4.21-273… 18226b51d911e09cd83657c99dd4506f ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_smp-2.4.21-273.x… 0489274cc30666eeec2be0127a669530 source rpm(s): ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/kernel-source-2.4.21-… 792149722a14f021aa095ec4fcc33976 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_deflt-2.4.21-273.sr… 9279c9a0613473a71057e76ab4b5a0e5 ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_smp-2.4.21-273.src.… 3bbd006852b9b8aab8a2868d922451d5 ______________________________________________________________________________ 5) pending vulnerabilities in SUSE Distributions and Workarounds: Please refer to our SUSE Security Summary report. ______________________________________________________________________________ 6) 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.7 (GNU/Linux) mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CohGBBARAgAGBQI7HmHDAAoJEJ5A4xAACqukTlQAoI4QzP9yjPohY7OU F7J3eKBTzp25AJ42BmtSd3pvm5ldmognWF3Trhp+GYkAlQMFEDe3O8IWkDf+zvyS FQEBAfkD/3GG5UgJj18UhYmh1gfjIlDcPAeqMwSytEHDENmHC+vlZQ/p0mT9tPiW tp34io54mwr+bLPN8l6B5GJNkbGvH6M+mO7R8Lj4nHL6pyAv3PQr83WyLHcaX7It Klj371/4yzKV6qpz43SGRK4MacLo2rNZ/dNej7lwPCtzCcFYwqkiiEYEEBECAAYF AjoaQqQACgkQx1KqMrDf94ArewCfWnTUDG5gNYkmHG4bYL8fQcizyA4An2eVo/n+ 3J2KRWSOhpAMsnMxtPbBiEYEExECAAYFAkGJG+YACgkQGsiRhDTRlzm8CQCg14Wz vg6j45e/r1oyt9EaHhleSacAnA+2dArk1I3xt49Z5rdnhqheF//9mQGiBDnu9IER BACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff4JctBsgs47tj miI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0dM+HFrruCgBlW t6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcOQliHu8jwRQHx lRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrKXBUX+K7u4ifr ZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBED3+D2t1V/f8l 0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUdG5sRA/9ovnc1 krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NMCC3Kj9aZHfA+ ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoEmyW/xC1sBbDk DUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNrYWdlIFNpZ25p bmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkDwmcABAsKAwQD FQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6dNfnwI2PAsgCg jH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCeQOMQAAqrpNzO AKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNeLZa/qM2JARUD BRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3tXXaJJp9pHMa4 fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBUD9i579uifklL snr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ30kNLWVXWATMn snT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot1ZPtB0lniw+/ xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpWcRgdn2DUVMmp U661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0EExECAB0FAjxq qTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1fAJ9dR7saz2KP NwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0EOe70khAIAISR 0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/HZnh3TwhBIw1 FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44ht5h+6HMBzoFC MAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPTtGzcAi2jVl9h l3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM523AMgpPQtsK m9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q2Y+GqZ+yAvNW jRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8QnSs0wwPg3xE ullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWawJxRLKH6Zjo/F aKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ1sj2xYdB1xO0 ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCHORrNjq9pYWlr xsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1wwylxadmmJaJ HzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQYEQIADAUCOe70 kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol0JdGwACeKTtt geVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAKCRCoTtronIAK yofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3coSPihn1+OBNw= =Fv2n - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQfEaXHey5gA9JdPZAQE8uAf/UDupbQayrLk1Tu6mm0u1FybBMmHmi1nx bj69KQRt5PjjYf1mkxHg65Z69oAjNLIjv+cCX8eJWc164ueiVpXgUzjqLouNgCcU dR266o+ZOlQXlTIv1HDLnU2D2yilOJz/EYk4OeGUh2wZNc+DLW7+rJ49qvPIsWBr ECZpwaOhIBOGicdS8i64b3AKW7gNV09Yru21/A/wn7QVfAAPMzQxDTn4/f2/ttxF 3E3xKURN1J9rSkGZMoX7BXK/4iLVurow8t8g2w6DMedyYvIuSLDyB3IlehLnhPmL uL2lSd1PK0rkGuVI6kTZL2lvDjfq4/CHf4MhHWGwDq88L+irqorMSQ== =xoll -----END PGP SIGNATURE-----

5 9

Pam issue, Winbind - sudo combination
by Ciro Iriarte 10 Feb '05

10 Feb '05

Well, i'll repost my question, because my first mail wasn't clear (i was in a hurry while writing it ). Have a Suse 9.2 Pro box authenticating against an NT Domain, i could join the domain, the users login, the homes get created automagically, all seems perfect, BUT, i'm having a little problem with sudo, any time an nt-domain-user runs it, sudo prompts for password (as it should), but it never accepts it!!. The original /etc/pam.d/sudo file looked like this: ------------------------------------------------------- #%PAM-1.0 auth required pam_unix2.so ------------------------------------------------------- Didn't find a Suse specific solution, tried a debian based one (the only one i've found), but it doesn't work, it looks like this: ------------------------------------------------------- #%PAM-1.0 auth sufficient pam_winbind.so auth required pam_unix2.so use_first_pass ------------------------------------------------------ Thanks in advanced. Ciro

3 5

Security patches for Suse's 2.6 kernel
by nordi 08 Feb '05

08 Feb '05

Hi list! I've ported the hardlink/symlink protection of the grsecurity patch to Suse's 2.6 kernels. My patch makes it considerable harder (and sometimes impossible) to exploit insecure handling of files in /tmp. Additionally it prevents some other annoying things that an attacker could do with hard/symlinks. The patch, more details and install instructions can be found on my website (http://private.addcom.de/nordi/). Feedback is welcome! The patch is very small and non-intrusive. The slightly changed handling of links should(!) not break existing software. At least I've been using this patch myself on a Suse 9.1 and a 9.2 machine for a couple of weeks now and haven't seen anything break that wasn't broken before ;) Regards nordi SHA1 checksums for the patches: Suse 9.2: d8138ce3da839aefa77a236ac0bd6436318ffc52 Suse 9.1: c7210821fa8c2ca87f2a4e2cb13646bdec36f72c

2 3

Help getting DMZ+reverse-proxy working
by Rainer Duffner 31 Jan '05

31 Jan '05

Hi, I have the following setup: LAN: 192.168.0.0/24 DMZ: 10.0.0.0/24 Internet: some DSL-connection, real IP. looks like this internal (192.168.0.0/24) ^ | | <----Internet----|FW|-->DMZ----10.0.0.0/24 I want to be able to access the webserver in the DMZ via port 443 (which works) and then reverse-proxy these requests to some internal IP on 192.168.0.0/24. That doesn't work. Here's what I have so far: FW_QUICKMODE="no" FW_DEV_EXT="eth-id-00:01:03:4c:cd:c0" FW_DEV_INT="eth-id-00:a0:24:a8:fb:a4" FW_DEV_DMZ="eth-id-00:04:76:13:6d:e5" FW_ROUTE="yes" FW_MASQUERADE="yes" FW_MASQ_DEV="$FW_DEV_EXT" FW_MASQ_NETS="0/0" FW_PROTECT_FROM_INTERNAL="no" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="ssh" FW_SERVICES_EXT_UDP="" FW_SERVICES_EXT_IP="" FW_SERVICES_EXT_RPC="" FW_SERVICES_DMZ_TCP="" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_IP="" FW_SERVICES_DMZ_RPC="" FW_SERVICES_INT_TCP="" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_SERVICES_INT_RPC="" FW_SERVICES_QUICK_TCP="" FW_SERVICES_QUICK_UDP="" FW_SERVICES_QUICK_IP="" FW_TRUSTED_NETS="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="no" FW_ALLOW_INCOMING_HIGHPORTS_UDP="DNS" FW_SERVICE_AUTODETECT="yes" FW_SERVICE_DNS="no" FW_SERVICE_DHCLIENT="no" FW_SERVICE_DHCPD="no" FW_SERVICE_SQUID="no" FW_SERVICE_SAMBA="no" FW_FORWARD="" FW_FORWARD_MASQ="0/0,10.0.0.x,tcp,443 10.0.0.x,192.168.0.y,tcp,80" FW_REDIRECT="" Any ideas how to do that ? Or do I need a real IP also in the DMZ ? cheers, Rainer -- =================================================== ~ Rainer Duffner - rainer(a)ultra-secure.de ~ ~ Freising - Munich - Germany ~ ~ Unix - Linux - BSD - OpenSource - Security ~ ~ http://www.ultra-secure.de/~rainer/pubkey.pgp ~ ===================================================

2 4

Basics needed: receive mail but mail header contains no 'for'
by Preusse, Mathias 31 Jan '05

31 Jan '05

Hi list, i need probably some basics. The mail header, so i can see it with outlook, seems to be broken. Example: Microsoft Mail Internet Headers Version 2.0 Received: from our.mailgateway.de ([a.b.c.d]) by internal.mailserver.de with Microsoft SMTPSVC(5.0.2195.5329); Mon, 31 Jan 2005 01:38:49 +0100 Received: from egan.earth9.com ([207.254.32.6]) by citation.freezemail.com (InterMail vK.4.04.00.00 781-3[3 This mail goes direktly to a user, not to a postbox for unknown user. It contains no 'for' or message id. I know, that any Mail header could be manipulated, but i thougt, there must be at last a target user (for) to sort it in a available postbox. Any hints or urls? best regards, Mathias Preusse

3 2

SuSE firewall and Elster
by Juergen.Mell＠t-online.de 31 Jan '05

31 Jan '05

Hi List, I have a problem with our current firewall setup and the German ELSTER tax program: I use SuSE 9.2 on our internet gateway. Right now, any direct traffic from the internal network to the internet is blocked by SuSE firewall and I have squid and postfix running on the gateway to allow web and e-mail traffic. As the elster program uses a propriatary protocol which cannot be fed through a proxy I now have to open the ports 8000 to 8006 which are used by this program for connections from the internal network to the internet. From what I found, this can be done with the iptables commands iptables -A FORWARD -i $INT -o $EXT -p TCP --dport 8000:8006 \ -j ACCEPT and iptables -A FORWARD -i $EXT -o $INT -m state \ --state ESTABLISHED,RELATED -p TCP --sport 8000 -j ACCEPT ($INT and $EXT are the internal resp. external interfaces) So far - so good. But what I am missing now is the masquerading of the IP address of the computer on the internal network (it gets a dynamic IP from the private address range 192.168.x.y). In the firewall script I have disabled masquerading (FW_MASQUERADE="no") to prevent any packets going out without using the squid proxy. Is there any way to open direct connections from the internal network _only_ for destination ports 8000 to 8006 without opening everything else (file-sharing networks etc.)? What iptables commands do I need for this purpose? Is there any better way to get this wounderful piece of software to work? Thank you for your help! Jürgen

4 5

Re: [suse-security] SuSE firewall and Elster
by Juergen.Mell＠t-online.de 30 Jan '05

30 Jan '05

On Sunday 30 January 2005 11:17, Jure Koren wrote: > On Sunday 30 January 2005 11:06, Jürgen Mell wrote: > > > iptables -t nat -A POSTROUTING -o $EXT -p tcp \ > > > --dport 8000:8006 -j SNAT --to-source <your static IP address> > > > > This does not work here. I always get > > iptables: No chain/target/match by that name > > iptables -t nat -n -L > > shows: > > Chain PREROUTING (policy ACCEPT) > > target prot opt source destination > > > > Chain POSTROUTING (policy ACCEPT) > > target prot opt source destination > > > > Chain OUTPUT (policy ACCEPT) > > target prot opt source destination > > > > Do you have any idea what is wrong here? > > Can you paste the exact iptables command you entered into the email? > > This usually happens when iptables is unable to load the target module > into the kernel, but SNAT and DNAT targets are part of the ip_conntrack > module, anyway, but MASQUERADE target is in a separate module, > ipt_MASQUERADE. Yes, that is the problem. The ipt_MASQUERADE module was not loaded and the computer was not booted after the last automatic kernel update from SuSE. Sorry, this is my fault. But now everything seems to work fine. > Another thing I noted is that your 8000-8006 range is for a specific > application that probably only connects to one server (or one remote > network). It would be wise to limit the destination of these connections > in the forward table to prevent users to use these ports to connect to > other servers on the internet. You can do this by adding "-d <your > elster server ip network>" to the outgoing FORWARD table entry. Yes, that's a good idea. Only problem here: there are 5 different servers on 5 IP addresses (on different networks) - and who knows when they will change these addresses. They do not even use host names but have the IPs hard-coded in the software. Sigh. Jürgen

2 1

LDAP and Kerberos
by info.bogenrieder＠sytech.de 28 Jan '05

28 Jan '05

Hi, I'm working on better security for my Server ( SuSE Pro 9.2) and decided to implement Kerberos(0.6.2-8, original heimdal rpm from SuSE 9.2) and LDAP (openldap2-2.2.15-5). I found this excellent howto: http://www.opentechnet.com/auth-howto/ar01s06.html. Now I have one Problem. I started to write my kerberos-information into the LDAP-Directory under the tree ou=kerberos,cn=exaple,cn=com just described on 6.2.1 to 6.2.7 when I change now the kerberos settings in my krb5.conf to [kdc] database = { realm = HIBYTE.DE dbname = ldap:dc=example,dc=com mkey_file = /var/heimdal/m-key } and make now a 'kadmin -l list *' the retrun is empty. In the syslog-fiel I see following entry: Jan 28 17:27:44 linux slapd[17048]: conn=44 fd=13 ACCEPT from PATH=/var/run/slapd/ldapi (PATH=/var/run/slapd/ldapi) Jan 28 17:27:44 linux slapd[17048]: conn=44 op=0 BIND dn="" method=163 Jan 28 17:27:44 linux slapd[17048]: conn=44 op=0 BIND authcid="uidnumber=0+gidnumber=0,cn=peercred,cn=external,cn=auth(a)EXAPLE.COM" Jan 28 17:27:44 linux slapd[17048]: conn=44 op=0 BIND dn="uidnumber=0+gidnumber=0,cn=peercred,cn=external,cn=auth" mech=EXTERNAL ssf=0 Jan 28 17:27:44 linux slapd[17048]: conn=44 op=1 SRCH base="dc=exaple.com,dc=de" scope=1 deref=0 filter="(objectClass=krb5KDCEntry)" Jan 28 17:27:44 linux slapd[17048]: conn=44 op=1 SRCH attr=krb5PrincipalName cn krb5PrincipalRealm krb5KeyVersionNumber krb5Key krb5ValidStart krb5ValidEnd krb5PasswordEnd krb5MaxLife krb5MaxRenew krb5KDCFlags krb5EncryptionType modifiersName modifyTimestamp creatorsName createTimestamp Jan 28 17:27:44 linux slapd[17048]: conn=44 op=1 SEARCH RESULT tag=101 err=0 nentries=0 text= Jan 28 17:27:44 linux slapd[17048]: conn=44 op=2 UNBIND Jan 28 17:27:44 linux slapd[17048]: conn=44 fd=13 closed If I change krb5.conf to [kdc] database = { realm = HIBYTE.DE dbname = ldap:ou=kerberos,dc=example,dc=com mkey_file = /var/heimdal/m-key } and then make a 'kadmin -l list *' I see all userer. I think the Problem is the searchscope of kerberos. In the logfile the scope is 1, is there a possibility to change this behavior to scope=2? Jörg

1 0

Re: [suse-security] SuSE-firewall with webserver and samba
by Birgit Kellner 28 Jan '05

28 Jan '05

Thanks to all who've helped so far. Here are a few further details. Christian Eisendle wrote: > In case of a slow network, the DNS-Server could be the reason for this > >problem, but after a refresh of the site (or maybe restart of the >browser) the website should be opened. >Are there any virtual hosts on the webserver? If not, users having >this problem could try to enter the IP-Adress of your webserver >instead of the DNS-Name, to determine if the name-resolving makes the >problems. > > > Indeed, some users who couldn't use the name can now access the server with the IP-Adress. From this I conclude that the problem must definitely be with the DNS-Server, or with network speed. The web server is registered with the central university administration, and they've told me it is entered correctly in their DNS server. I can't readily compare nslookup output from outside the university and inside because I'm inside the university network even if I connect from home, but I'll try to get someone to do that for me. As for the samba problem: >What's the exact problem? Is it a connection or an authenticating >problem? At first try to connect with the ip-adress instead of the >netbios name (\\222.222.222.x\share) >Does a telnet to samba server on port 139 work? >Does it work, when SuSEfirewall2 is stopped? > > > > 1) Connection with IP-Address works. 2) telnet is disabled on the server. an ssh connection on that port doesn't work. 3) the connection works without the firewall, even with the server name, and not only with the ip address. with the firewall, it only works with the ip address. The firewall configuration file now looks like this: FW_QUICKMODE="no" FW_DEV_EXT="eth0" FW_DEV_INT="" FW_MASQUERADE="no" FW_PROTECT_FROM_INTERNAL="yes" FW_AUTOPROTECT_SERVICES="yes" FW_SERVICES_EXT_TCP="22 80 ssh www" FW_SERVICES_EXT_UDP="" FW_SERVICES_EXT_IP="" FW_SERVICES_INT_TCP="" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_TRUSTED_NETS="131.130.180.0/25,tcp,137 131.130.180.0/25,tcp,138 131.130.180.0/25,tcp,139 131.130.180.0/25,tcp,445 131.130.180.0/25,udp,137 131.130.180.0/25,udp,138 131.130.180.0/25,udp,139 131.130.180.0/25,udp,445" FW_ALLOW_INCOMING_HIGHPORTS_TCP="dns" FW_ALLOW_INCOMING_HIGHPORTS_UDP="dns" FW_SERVICE_AUTODETECT="yes" FW_SERVICE_SAMBA="yes" FW_LOG_DROP_CRIT="yes" FW_LOG_DROP_ALL="yes" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_ACCEPT_ALL="no" FW_KERNEL_SECURITY="yes" FW_ALLOW_PING_FW="no" FW_ALLOW_PING_EXT="no" FW_IPSEC_TRUST="no" FW_DEV_DMZ="" FW_SERVICES_DMZ_IP="" FW_SERVICES_DMZ_UDP="" FW_SERVICES_DMZ_TCP="" FW_MASQ_NETS="" FW_ROUTE="no" FW_ALLOW_FW_TRACEROUTE="yes" This is my smb.conf: [global] workgroup = ISTB netbios name = ISTB server server string = ISTB fileserver on %h encrypt passwords = yes invalid users = root hosts allow = 222.222.222.0/25 localhost load printers = no passdb backend = smbpasswd:/etc/samba/smbpasswd [data] comment = ISTB Kollektivverzeichnis volume = ISTB-Kollektiv path = /istb_userdata browseable = yes writeable = yes guest ok = no valid users = istb_user read list = istb_user write list = istb_user Thanks again, Birgit

2 1

Re: AW: [suse-security] SuSE-firewall with webserver and samba
by Birgit Kellner 27 Jan '05

27 Jan '05

Christian Eisendle - asut computer wrote: >Hi Birgit! > >What does the logfile say? > >Try to install "iptraf" (also included in the suse distribution - maybe >it is already installed :) > >Stop the firewall, start iptraf, choose "IP traffic monitor" and select >your network interface. >Now try to connect to the samba server with the server-name and look at >the output of iptraf - it shows you any IP-connections. >Have a look at the tcp and udp ports, which are used and include them in >your firewall configuration. > >HTH > >Christian > > > Hi Christian, thanks! iptraf shows tcp traffic on ports 139 and 445. both are already open to the trusted net in the firewall. I've now tried to enter one specific IP address in FW_TRUSTED_NETS, rather than a block in the notation 222.222.222.0/25. With this changed setting, access works. So it seems that my FW_TRUSTED_NETS syntax was wrong after all. But what would be the right way to enter a whole block? Confused greetings, Birgit

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

openSUSE Security January 2005