Linux Today: Linux News On Internet Time.

More on LinuxToday

Advisories: April 4, 2005

Apr 05, 2005, 04:45 (0 Talkback[s])

Conectiva Linux


SUMMARY : Fixes for several mysql vulnerabilities
DATE : 2005-04-04 13:52:00
ID : CLA-2005:946

MySQL[1] is a very popular SQL database.

This announcement fixes several vulnerabilities discovered in MySQL:

MySQL allowed remote authenticated users with INSERT and DELETE privileges on 'mysql' administrative database to execute arbitrary code by using CREATE FUNCTION to access libc calls.

MySQL allowed remote authenticated users with INSERT and DELETE privileges on 'mysql' administrative database to bypass library path restrictions and execute arbitrary libraries by using INSERT INTO to modify the mysql.func table, which is processed by the udf_init function.

MySQL used predictable file names when creating temporary tables, which allowed local users with CREATE TEMPORARY TABLE privileges to overwrite arbitrary files via a symlink attack.

We recommend that all MySQL users upgrade their packages as soon as possible.

IMPORTANT: after the upgrade at Conectiva Linux 9, the mysql service must be restarted manually. In order to do that, run the following command as root:

# /sbin/service mysql restart



The apt tool can be used to perform RPM packages upgrades:

  • run: apt-get update
  • after that, execute: apt-get upgrade

Detailed instructions regarding the use of apt and upgrade examples can be found at http://distro.conectiva.com.br/atualizacoes/#apt?idioma=en

All packages are signed with Conectiva's GPG key. The key and instructions on how to import it can be found at
http://distro.conectiva.com.br/seguranca/chave/?idioma=en Instructions on how to check the signatures of the RPM packages can be found at http://distro.conectiva.com.br/seguranca/politica/?idioma=en
All our advisories and generic update instructions can be viewed at http://distro.conectiva.com.br/atualizacoes/?idioma=en
Copyright (c) 2004 Conectiva Inc.

Debian GNU/Linux

Debian Security Advisory DSA 704-1 security@debian.org
http://www.debian.org/security/ Martin Schulze April 4th, 2005 http://www.debian.org/security/faq

Package : remstats
Vulnerability : tempfile, missing input sanitising
Problem-Type : local, remote
Debian-specific: no
CVE IDs : CAN-2005-0387 CAN-2005-0388

Jens Steube discovered several vulnerabilities in remstats, the remote statistics system. The Common Vulnerabilities and Exposures Project identifies the following problems:


When processing uptime data on the unix-server a temporary file is opened in an insecure fashion which could be used for a symlink attack to create or overwrite arbitrary files with the permissions of the remstats user.


The remoteping service can be exploited to execute arbitrary commands due to missing input sanitising.

For the stable distribution (woody) these problems have been fixed in version 1.00a4-8woody1.

For the unstable distribution (sid) these problems have been fixed in version 1.0.13a-5.

We recommend that you upgrade your remstats packages.

Upgrade Instructions

wget url

will fetch the file for you
dpkg -i file.deb

will install the referenced file.

If you are using the apt-get package manager, use the line for sources.list as given below:

apt-get update

will update the internal database apt-get upgrade

will install corrected packages

You may use an automated update by adding the resources from the footer to the proper configuration.

Debian GNU/Linux 3.0 alias woody

Source archives:

Size/MD5 checksum: 700 5efc205ed693b60a221482d34f806328
Size/MD5 checksum: 18811 2aeb52cab7aad8a500a96d29b3930750
Size/MD5 checksum: 918361 dd857cd7d66037ce068df01d22b4cee9

Architecture independent components:

Size/MD5 checksum: 171294 08f1461cfeff2282a1b573d329bb3ed1
Size/MD5 checksum: 73580 568da9f07f8e229245c32a8c9690fd4a
Size/MD5 checksum: 246540 5bae0a115c1fe653793df17d61eacdad

Alpha architecture:

Size/MD5 checksum: 60664 761461ec410d5dac63378df866be6cad

ARM architecture:

Size/MD5 checksum: 48028 e1e45ef582d1a82cd76d16d09fc63c5b

Intel IA-32 architecture:

Size/MD5 checksum: 46094 daf29132eb3252d957d4517447f2cbae

Intel IA-64 architecture:

Size/MD5 checksum: 63346 dd6cfabb3329b80507b62d3b3d4f8b82

HP Precision architecture:

Size/MD5 checksum: 49794 d9c9867d122221a0d99cdfa0a774e3dd

Motorola 680x0 architecture:

Size/MD5 checksum: 45004 9a15c54ea425443dfa776bd61cff2c2a

Big endian MIPS architecture:

Size/MD5 checksum: 50662 b79c01e63e63b0ca39016c69e81b75a1

Little endian MIPS architecture:

Size/MD5 checksum: 50614 ca121e22f5cb4167a08a52fea2a4c7f0

PowerPC architecture:

Size/MD5 checksum: 48894 61528468c5735dda7a75439735cab676

IBM S/390 architecture:

Size/MD5 checksum: 47900 bc9b4cae98fce8dd9477d67625dda5fe

Sun Sparc architecture:

Size/MD5 checksum: 52176 283ade4294f9f7dc751a038770035dd8

These files will probably be moved into the stable distribution on its next update.

Debian Security Advisory DSA 705-1 security@debian.org
http://www.debian.org/security/ Martin Schulze
April 4th, 2005 http://www.debian.org/security/faq

Package : wu-ftpd
Vulnerability : missing input sanitising
Problem-Type : remote
Debian-specific: no
CVE IDs : CAN-2005-0256 CAN-2003-0854

Several denial of service conditions have been discovered in wu-ftpd, the popular FTP daemon. The Common Vulnerabilities and Exposures project identifies the following problems:


Adam Zabrocki discovered a denial of service condition in wu-ftpd that could be exploited by a remote user and cause the server to slow down the server by resource exhaustion.


Georgi Guninski discovered that /bin/ls may be called from within wu-ftpd in a way that will result in large memory consumption and hence slow down the server.

For the stable distribution (woody) these problems have been fixed in version 2.6.2-3woody5.

For the unstable distribution (sid) these problems have been fixed in version 2.6.2-19.

We recommend that you upgrade your wu-ftpd package.

Upgrade Instructions

wget url

will fetch the file for you
dpkg -i file.deb

will install the referenced file.

If you are using the apt-get package manager, use the line for sources.list as given below:

apt-get update

will update the internal database apt-get upgrade

will install corrected packages

You may use an automated update by adding the resources from the footer to the proper configuration.

Debian GNU/Linux 3.0 alias woody

Source archives:

Size/MD5 checksum: 607 78463b3882e0d32102344bb0580e0d98
Size/MD5 checksum: 101661 967b719c02892c867ad0d6456a5dd47a
Size/MD5 checksum: 354784 b3c271f02aadf663b8811d1bff9da3f6

Architecture independent components:

Size/MD5 checksum: 3484 cc6ee1aeb156077af311870f095840ab

Alpha architecture:

Size/MD5 checksum: 292630 c164f9f2d0ae5d70587ca49ddbe543b4

ARM architecture:

Size/MD5 checksum: 265840 c86cdbc78969f755dce0facce4a1f882

Intel IA-32 architecture:

Size/MD5 checksum: 255216 504af14aec48191405c08a56845d330b

Intel IA-64 architecture:

Size/MD5 checksum: 321932 ced4192d937ccedfa5a7ab2e9e77c378

HP Precision architecture:

Size/MD5 checksum: 276624 4a1b5b6115ed1d93206c9787e8d37038

Motorola 680x0 architecture:

Size/MD5 checksum: 249810 e873e950d3b234a7854ee0e4810783f5

Big endian MIPS architecture:

Size/MD5 checksum: 273426 364c07d6a21f8aab43b3841ce98df8c6

Little endian MIPS architecture:

Size/MD5 checksum: 273568 4e51f44342035b6ecafc624b1a6c06f3

PowerPC architecture:

Size/MD5 checksum: 268816 4072fbbb73bd8013b9a191f3aa7bd778

IBM S/390 architecture:

Size/MD5 checksum: 263638 d86fc84ab2974a80fd7407d826d8b003

Sun Sparc architecture:

Size/MD5 checksum: 270784 1110401bccc9035cc1b30eb8146aee18

These files will probably be moved into the stable distribution on its next update.

For apt-get: deb http://security.debian.org/ stable/updates main
For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
Mailing list: debian-security-announce@lists.debian.org
Package info: `apt-cache show <pkg>' and http://packages.debian.org/<pkg>

Gentoo Linux

Gentoo Linux Security Advisory GLSA 200504-03


Severity: Low
Title: Dnsmasq: Poisoning and Denial of Service vulnerabilities
Date: April 04, 2005
Bugs: #86718
ID: 200504-03


Dnsmasq is vulnerable to DNS cache poisoning attacks and a potential Denial of Service from the local network.


Dnsmasq is a lightweight and easily-configurable DNS forwarder and DHCP server.

Affected packages

     Package          /  Vulnerable  /                      Unaffected

  1  net-dns/dnsmasq       < 2.22                              >= 2.22


Dnsmasq does not properly detect that DNS replies received do not correspond to any DNS query that was sent. Rob Holland of the Gentoo Linux Security Audit team also discovered two off-by-one buffer overflows that could crash DHCP lease files parsing.


A remote attacker could send malicious answers to insert arbitrary DNS data into the Dnsmasq cache. These attacks would in turn help an attacker to perform man-in-the-middle and site impersonation attacks. The buffer overflows might allow an attacker on the local network to crash Dnsmasq upon restart.


There is no known workaround at this time.


All Dnsmasq users should upgrade to the latest version:

    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-dns/dnsmasq-2.22"


[ 1 ] Dnsmasq Changelog



This GLSA and any updates to it are available for viewing at the Gentoo Security Website:



Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at http://bugs.gentoo.org.


Copyright 2005 Gentoo Foundation, Inc; referenced text belongs to its owner(s).

The contents of this document are licensed under the Creative Commons - Attribution / Share Alike license.


SUSE Linux

SUSE Security Announcement

Package: kernel
Announcement-ID: SUSE-SA:2005:021
Date: Mon, 04 Apr 2005 12:00:00 +0000
Affected products: 8.2, 9.0, 9.2 SUSE Linux Desktop 1.0 SUSE Linux Enterprise Server 8
Vulnerability Type: local privilege escalation
Severity (1-10): 6
SUSE default package: yes
Cross References: CAN-2005-0750

Content of this advisory:

  1. security vulnerability resolved: local root exploit in bluetooth network stack problem description
  2. solution/workaround
  3. special instructions and notes
  4. package location and checksums
  5. pending vulnerabilities, solutions, workarounds: See SUSE Security Summary Report.
  6. standard appendix (further information)

1) problem description, brief discussion

This Linux kernel security update fixes a problem within the Bluetooth kernel stack which can be used by a local attacker to gain root access or crash the machine.

To exploit this problem, the Bluetooth modules do not need to be loaded since they are auto loaded on demand (except in products mentioned below).

This problem has been assigned the Mitre CVE ID CAN-2005-0750.

Updated packages have been provided for the default affected products:

  • SUSE Linux 8.2, 9.0 and 9.2 (both i386 and x86_64) - SUSE Linux Enterprise Server 8 (i386, ia64 and x86_64) - SUSE Linux Desktop 1.0

Other architectures do not have Bluetooth enabled. Also SUSE Linux 9.1, SUSE Linux Enterprise Server 9 and Novell Linux Desktop 9 are not affected by default since the Bluetooth module is not auto loaded. These will get the patch with the next security update.

2) solution/workaround

Please install the updated packages.

A workaround is to disable Bluetooth by using:

  • Remove or move away the bluetooth core module.

    On 2.6 kernels this is the file:
    /lib/modules/<kernel version>/kernel/net/bluetooth/bluetooth.ko

    On 2.4 kernels this is the file:
    /lib/modules/<kernel version>/kernel/net/bluetooth/bluez.o

  • Disable auto load of the bluetooth protocol module by commenting out the line:
    alias net-pf-31 bluez

    in /etc/modules.conf (2.4 systems) or the line:
    alias net-pf-31 bluetooth

    in /etc/modprobe.conf (2.6 systems).

    Make sure the module is not loaded, or run "rmmod bluetooth" / "rmmod bluez".

3) special instructions and notes


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/.


    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.

  • 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


    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


  • 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

    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/Intel-536ep-4.69-5.7.i586.rpm 83cf3ebb75d4e1a7e435dd13ee2d8d1c
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-bigsmp-2.6.8-24.14.i586.rpm 0fb1469b42bf62e5cc87cb4f1410ef09
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-bigsmp-nongpl-2.6.8-24.14.i586.rpm 970d200f0f0abd9025f858abc575c5b7
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-default-2.6.8-24.14.i586.rpm ba4fdb46b50cd7b09824cbedc61bfc8c
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-default-nongpl-2.6.8-24.14.i586.rpm 20d97e2d55dc5433f70e02e270ba13c5
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-smp-2.6.8-24.14.i586.rpm 600ce2e1f6fe06d2db4f0f4bdf1797b6
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-smp-nongpl-2.6.8-24.14.i586.rpm ed5aaf51f97ae8a8e7bd0992e6982a69
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-source-2.6.8-24.14.i586.rpm 0dd5cffcda797bbdd4cbee53f5a5d05d
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-syms-2.6.8-24.14.i586.rpm d74094729d1046f491e36950d3155d26
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-um-2.6.8-24.14.i586.rpm e37de6a488da1887ae1f8eee94ceeef3
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/kernel-um-nongpl-2.6.8-24.14.i586.rpm 81b454e91fde4128b9185aafd9012666
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/ltmodem-8.31a8-6.7.i586.rpm 2c8bc429e498cd79f9528847efcd0c08
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/um-host-install-initrd-1.0-48.7.i586.rpm 0f31340cd661a5e8c9fa04068e2c5097
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/um-host-kernel-2.6.8-24.14.i586.rpm f80c2529732a36436cc16fed1a5214bb
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/noarch/kernel-docs-2.6.8-24.14.noarch.rpm a92ea90e592e9e7a5c1a953c69963010

SUSE Linux 9.0:
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/Intel-536ep-4.62-24.i586.rpm 2245daa3986b2befb607e0ca71dfb818
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/Intel-v92ham-4.53-24.i586.rpm ef15111940735dd59964d2356fad9daf
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_athlon-2.4.21-286.i586.rpm d24065275f61694a7a241c7782b60a8d
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-286.i586.rpm 1480147c870224583cfc8047f6cc8827
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp-2.4.21-286.i586.rpm 0924f45e191c17a0fd18868f25d661af
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_smp4G-2.4.21-286.i586.rpm 72683d1de2eff870248794f3617e2f0d
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/k_um-2.4.21-286.i586.rpm 183a596c6c7a61aac6f477c67f9d31f8
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/kernel-source-2.4.21-286.i586.rpm 52b637e3f0ab4c715ccba423b7560604
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/ltmodem-8.26a-213.i586.rpm 960a99f0100ff6ef63d538c0be693130 source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/Intel-536ep-4.62-24.src.rpm 2abdcc2913cb35d6c63aa60436cf317a
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/Intel-v92ham-4.53-24.src.rpm 66cbb800b7f7a7c272db41a09d85ca06
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_athlon-2.4.21-286.src.rpm 795048442b07da36f9615364a4d4776f
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_deflt-2.4.21-286.src.rpm ef1ad2e167cb18e730d2203cfc4cc79a
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp-2.4.21-286.src.rpm 7649239b72c5ef11e5af2a54de1f9112
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_smp4G-2.4.21-286.src.rpm fc6e4f0553621438ccc950d60d4ae95a
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/k_um-2.4.21-286.src.rpm 14934af7134d786d5229c9ca7793ac0c
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/kernel-source-2.4.21-286.src.rpm feb614d9a26cebce682ebfcc695c19ab
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/ltmodem-8.26a-213.src.rpm 0e8609ae41f93d7e23e69fb5ba426ca8

SUSE Linux 8.2:
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_athlon-2.4.20-133.i586.rpm 820c50323c4e7f529fc045c25320db33
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_deflt-2.4.20-133.i586.rpm e9fffc1da0665f6634622e57ebdd2d56
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_psmp-2.4.20-133.i586.rpm 679a02afce5b9514bcf0b8499a29bc82
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/k_smp-2.4.20-133.i586.rpm 717bf34a3641a5bf0f8ccf26990442d2
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/kernel-source-2.4.20.SuSE-133.i586.rpm 79ad972a1204c25fa5b8722500f1cbe3 source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_athlon-2.4.20-133.src.rpm 0641b2ad5043d15f4d21dd8d59337b07
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_deflt-2.4.20-133.src.rpm c9345e663d84eddca48b7260b509ef10
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_psmp-2.4.20-133.src.rpm c3caebe80385586f79e0ac4bb2b7099b
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/k_smp-2.4.20-133.src.rpm 0161fd5bb0b97af8d33dbfbf39cb3f89
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/kernel-source-2.4.20.SuSE-133.src.rpm d896e620182157894085729ea98e0e40

x86-64 Platform:

SUSE Linux 9.2:
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/kernel-default-2.6.8-24.14.x86_64.rpm 00daf3e5ccda0243add47e6b31d3b324
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/kernel-default-nongpl-2.6.8-24.14.x86_64.rpm 000e1ebe2effe50862866c4bb895b6b1
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/kernel-smp-2.6.8-24.14.x86_64.rpm 24a87872b72f82569cc48b4e4937625e
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/kernel-smp-nongpl-2.6.8-24.14.x86_64.rpm 6678d95a894a6068556a0679fe2804c4
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/kernel-source-2.6.8-24.14.x86_64.rpm 9243499a1e2d3d187b03e9648efedc9a
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/x86_64/kernel-syms-2.6.8-24.14.x86_64.rpm 4e6efe583cb0b017bf74fbc31cf0f4ec source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-default-2.6.8-24.14.nosrc.rpm 2ec696edcbbcee3467506185cdff6cde
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-smp-2.6.8-24.14.nosrc.rpm 706bdd002d12f682536b63ad92ca3c35
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-source-2.6.8-24.14.src.rpm 254a7e8f8284539862309249767819fc
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/kernel-syms-2.6.8-24.14.src.rpm 1c3bd22089eff61c8a9fc27e15b5d569

SUSE Linux 9.0:
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_deflt-2.4.21-286.x86_64.rpm 494a414468b1b4ab035610b749f8c7fa
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/k_smp-2.4.21-286.x86_64.rpm d60ae1bf9a4fdfcf0d2adfc15dbecf2b
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/kernel-source-2.4.21-286.x86_64.rpm b2575d169b38f1058176874919dbbb63 source rpm(s):
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_deflt-2.4.21-286.src.rpm b9a11390529505e1c824bdea4d5eecec
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/k_smp-2.4.21-286.src.rpm 562198014fbdf598f131510cefe14d47
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/kernel-source-2.4.21-286.src.rpm 99e2df1ec59dfa89c18077465cd63660

5) Pending vulnerabilities in SUSE Distributions and Workarounds:

See 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.
    3. 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@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.
    4. 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:
      1. gpg is installed
      2. 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@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:


  • general/linux/SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe@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@suse.com>.

    For general information or the frequently asked questions (faq) send mail to:

    <suse-security-info@suse.com> or <suse-security-faq@suse.com> respectively.

SUSE's security contact is <security@suse.com> or <security@suse.de>. @suse.de>.

The <security@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@suse.de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>

Ubuntu Linux

Ubuntu Security Notice USN-104-1 April 04, 2005
sharutils vulnerability

A security issue affects the following Ubuntu releases:

Ubuntu 4.10 (Warty Warthog)

The following packages are affected:


The problem can be corrected by upgrading the affected package to version 1:4.2.1-10ubuntu0.2. In general, a standard system upgrade is sufficient to effect the necessary changes.

Details follow:

Joey Hess discovered that "unshar" created temporary files in an insecure manner. This could allow a symbolic link attack to create or overwrite arbitrary files with the privileges of the user invoking the program.

Source archives:

Size/MD5: 8181 7135804300d9a381cfebc2133e7239c2
Size/MD5: 634 1a16efd9010325d369909b608fb59597
Size/MD5: 306022 b8ba1d409f07edcb335ff72a27bd9828

Architecture independent packages:

Size/MD5: 28000 56cd083b2fbc3e689cb157a59c760f52

amd64 architecture (Athlon64, Opteron, EM64T Xeon)

Size/MD5: 113908 801afa19d2f272d22f7d13f5efb0a51a

i386 architecture (x86 compatible Intel/AMD)

Size/MD5: 110766 2d3e74efceff274a2bb4a17b3c4702b1

powerpc architecture (Apple Macintosh G3/G4/G5)

Size/MD5: 112656 1ce41914dde0c8d548f6bcc2d3a8fbd8