Users login

Create an account »

JOIN XATRIX

Users login

Home » Hacking News » SuSE-SA:2002:018-lukemftp, nkitb, nkitserv

SuSE-SA:2002:018-lukemftp, nkitb, nkitserv

by Nikola Strahija on May 16th, 2002 Content of this advisory: 1) security vulnerability resolved: buffer overflow while parsing PASV command problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information)


1) problem description, brief discussion, solution, upgrade information

Lukemftp (ftp(1), /usr/bin/ftp, /usr/bin/pftp) is a compfortable ftp
client from NetBSD.
A buffer overflow could be triggered by an malicious ftp server while the
client parses the PASV ftp command. An attacker who control an ftp server
to which a client using lukemftp is connected can gain remote access to
the clients machine with the privileges of the user running lukeftp.

The lukemftp RPM package is installed by default.
You need to update the package, as no temporary workaround is possbible.

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.



i386 Intel Platform:

SuSE-8.0
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/lukemftp-1.5-249.i386.rpm
0ae28f7ca49157bfa5783626d3e82cef
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/lukemftp-1.5-249.src.rpm
d9fc530c338ea2de122b6a4a1f89a627

SuSE-7.3
ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/lukemftp-1.5-256.i386.rpm
aeb64a5ba64b5b334dfcf244423a9809
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/lukemftp-1.5-256.src.rpm
cc94b939696c76cda0fec683d12ff384

SuSE-7.2
ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/lukemftp-1.5-256.i386.rpm
94812aeb3b164a67b0c85b0c9a61a450
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/lukemftp-1.5-256.src.rpm
5cd6642505a68be70ce9eac3ba5dd311

SuSE-7.1
ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/lukemftp-1.5-251.i386.rpm
836df6046ce81fcc82e9939fde5003d1
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/lukemftp-1.5-251.src.rpm
788bc38fed7b486e857b5d780451b7a7

SuSE-7.0
ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/nkitb-2002.5.8-0.i386.rpm
e6199c28c700461a7ae10c3f7fba73a8
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/nkitb-2002.5.8-0.src.rpm
e1c6379846842ea62a5c484167102cae

SuSE-7.0

ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/nkitserv-2002.5.8-0.i386.rpm
50bb6a7ae3f450ad530ad92ae8dad3e1

SuSE-6.4
ftp://ftp.suse.com/pub/suse/i386/update/6.4/a1/nkitb-2002.5.9-0.i386.rpm
6950a272cf3a30a02860cf179387a9e8
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/nkitb-2002.5.9-0.src.rpm
09d7ac9ba5e1420eeddb016a6d812067



Sparc Platform:

SuSE-7.3
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/lukemftp-1.5-77.sparc.rpm
295d90e7bfeb94f27f542616e016bd65
source rpm:
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/lukemftp-1.5-77.src.rpm
42e213cfc930e0a00aa871e9996d3cba

SuSE-7.1
ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n1/lukemftp-1.5-76.sparc.rpm
50fc0f99b42347aee746450624ed4817
source rpm:
ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/lukemftp-1.5-76.src.rpm
01cdff7ff9f908466b8d3269fe4529c5

SuSE-7.0

ftp://ftp.suse.com/pub/suse/sparc/update/7.0/a1/nkitb-2002.5.8-0.sparc.rpm
210230a1a085af9f777f047a9edfa9f5
source rpm:
ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/nkitb-2002.5.8-0.src.rpm
b0e476e5ba4e9211cab20442f35b49d8

SuSE-7.0

ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/nkitserv-2002.5.8-0.sparc.rpm
70b063b1901c8655a23b008cc6ef4036



AXP Alpha Platform:

SuSE-7.1
ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/lukemftp-1.5-89.alpha.rpm
27c6ca255ef42c7e6851f309d6474fcd
source rpm:
ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/lukemftp-1.5-89.src.rpm
fdc27d3abae5bf6dfcd06907d2afc278

SuSE-7.0
ftp://ftp.suse.com/pub/suse/axp/update/7.0/a1/nkitb-2002.5.8-0.alpha.rpm
2c397f234a2326baba98a4da8dff601a
source rpm:
ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/nkitb-2002.5.8-0.src.rpm
437a49653372205c4218e7283422fd6b

SuSE-7.0

ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/nkitserv-2002.5.8-0.alpha.rpm
e2943d09b3bf82883bfd62aff74e500b

SuSE-6.4
ftp://ftp.suse.com/pub/suse/axp/update/6.4/a1/nkitb-2002.5.9-0.alpha.rpm
33b7a7b2f81dc78035450c0643786c83
source rpm:
ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/nkitb-2002.5.9-0.src.rpm
60960a0129207b317fc22089f6203589



PPC Power PC Platform:

SuSE-7.3
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/lukemftp-1.5-154.ppc.rpm
fd6bc23e95cd7a19283dd4067f376bb3
source rpm:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/lukemftp-1.5-154.src.rpm
bb301c6487a09a2b3d82ce9b000b8f69

SuSE-7.1
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/lukemftp-1.5-150.ppc.rpm
023a43cba32d976d0a5665365242647b
source rpm:
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/lukemftp-1.5-150.src.rpm
53f38c8f4a3205b3bedbc76b209d177b

SuSE-7.0
ftp://ftp.suse.com/pub/suse/ppc/update/7.0/a1/nkitb-2002.5.8-0.ppc.rpm
101d5af039c262f7b7e7d50598fa064c
source rpm:
ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/nkitb-2002.5.8-0.src.rpm
ed39244bcb57fad7b92287f5c9d26e3d

SuSE-7.0
ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/nkitserv-2002.5.8-0.ppc.rpm
b6146585ab16d1d507e04f066f21f5d6

SuSE-6.4
ftp://ftp.suse.com/pub/suse/ppc/update/6.4/a1/nkitb-2002.5.9-0.ppc.rpm
10b66b58b887a1899df7e16b15689bfb
source rpm:
ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/nkitb-2002.5.9-0.src.rpm
954dcd26ef2eb777e737621927f98835


______________________________________________________________________________

2) Pending vulnerabilities in SuSE Distributions and Workarounds:

- imap
A bug report about a buffer overflow in the RFC1730 code of the wu-imap
eMail server was published. SuSE Linux' imap packages were compiled
without RFC1730 support, so SuSE Linux is not vulnerable to this bug per
default.

- dhcp
A format string bug was found in the DynamicDNS (DDNS) code of ISC's
DHCP server software. New RPMs are currently being build.

- imlib
Due to packaging failures we have to re-release the imlib packages
which should be available within the next days. This update addresses
missing dependencies and affects applications like xcdroast.

- perl-Digest-MD5
A bug was found in the UTF8 interaction between perl and perl-Digest-MD5
which leads into failures while verifying the MD5 hash.
New RPMs are currently being build.

______________________________________________________________________________

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
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 [email protected]),
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
to verify the signature of the package, where is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an uninstalled 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 .

[email protected]
- SuSE's announce-only mailing list.
Only SuSE's security annoucements are sent to this list.
To subscribe, send an email to
.

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

=====================================================================
SuSE's security contact is or .
The 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 cleartext 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
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key


Newsletter signup

Signup to our monthly newsletter and stay in touch with IT news!

Free E-books

We've got ebooks! But they're not online. :( Please give us a few days to bring downloads back.

Contact

Have something to say or just wanna drop us a line? Please keep this in mind: to spam, we reply with spam.

Contact us »