Advisories: April 4, 2005 Apr 5, 2005, 04 :45 UTC (0 Talkback[s]) (2552 reads)
Conectiva Linux
CONECTIVA LINUX SECURITY ANNOUNCEMENT
PACKAGE : MySQL
SUMMARY : Fixes for several mysql vulnerabilities
DATE : 2005-04-04 13:52:00
ID : CLA-2005:946
RELEVANT RELEASES : 9, 10
DESCRIPTION
MySQL[1] is a very popular SQL database.
This announcement fixes several vulnerabilities discovered in MySQL:
1.CAN-2005-0709[2]
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.
2.CAN-2005-0710[3]
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.
3.CAN-2005-0711[4]
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.
SOLUTION
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:
Jens Steube discovered several vulnerabilities in remstats, the remote
statistics system. The Common Vulnerabilities and Exposures Project
identifies the following problems:
CAN-2005-0387
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.
CAN-2005-0388
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.
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:
CAN-2005-0256
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.
CAN-2003-0854
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.
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.
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.
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:
security vulnerability resolved:
local root exploit in bluetooth network stack
problem description
solution/workaround
special instructions and notes
package location and checksums
pending vulnerabilities, solutions, workarounds:
See SUSE Security Summary Report.
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".
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.
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
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.
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:
md5sums as provided in the (cryptographically signed) announcement.
using the internal gpg signatures of the rpm package.
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.
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:
gpg is installed
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:
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>
A security issue affects the following Ubuntu releases:
Ubuntu 4.10 (Warty Warthog)
The following packages are affected:
sharutils
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.
