3571e53040
patches for easier mirroring, to eliminate a special copy, to make www.freebsd.org/security a full copy of security.freebsd.org and be eventually be the same. For now files are just sitting there. The symlinks are missing. Discussed on: www (repository location) Discussed with: simon (so)
101 lines
3.5 KiB
Text
101 lines
3.5 KiB
Text
-----BEGIN PGP SIGNED MESSAGE-----
|
|
|
|
=============================================================================
|
|
FreeBSD-SA-01:47 Security Advisory
|
|
FreeBSD, Inc.
|
|
|
|
Topic: xinetd contains multiple vulnerabilities
|
|
|
|
Category: ports
|
|
Module: xinetd
|
|
Announced: 2001-07-10
|
|
Credits: zen-parse@gmx.net
|
|
Affects: Ports collection prior to the correction date.
|
|
Corrected: 2001-06-30
|
|
Vendor status: Updated version released
|
|
FreeBSD only: NO
|
|
|
|
I. Background
|
|
|
|
xinetd is a replacement for inetd, the internet super-server.
|
|
|
|
II. Problem Description
|
|
|
|
The xinetd port, versions prior to xinetd-2.3.0, contains a
|
|
potentially exploitable buffer overflow in the logging routines.
|
|
If xinetd is configured to log the userid of remote clients obtained
|
|
via the RFC1413 ident service, a remote user may be able to cause
|
|
xinetd to crash by returning a specially-crafted ident response. This
|
|
may also potentially execute arbitrary code as the user running
|
|
xinetd, normally root.
|
|
|
|
In addition, xinetd used a default umask of 0. This may
|
|
inadvertently cause applications started by xinetd to create
|
|
world-writable files unless the applications explicitely set the
|
|
umask.
|
|
|
|
The xinetd port is not installed by default, nor is it "part of
|
|
FreeBSD" as such: it is part of the FreeBSD ports collection, which
|
|
contains over 5400 third-party applications in a ready-to-install
|
|
format. The ports collection shipped with FreeBSD 4.3 is vulnerable
|
|
to this problem since it was discovered after its release.
|
|
|
|
FreeBSD makes no claim about the security of these third-party
|
|
applications, although an effort is underway to provide a security
|
|
audit of the most security-critical ports.
|
|
|
|
III. Impact
|
|
|
|
Remote users may be able to cause xinetd to crash and potentially
|
|
execute arbitrary code as the user running xinetd.
|
|
|
|
Processes started by xinetd may inadvertently use a umask of 0, causing
|
|
files created by these processes to by world-writable.
|
|
|
|
If you have not chosen to install the xinetd port/package, then
|
|
your system is not vulnerable to this problem.
|
|
|
|
IV. Workaround
|
|
|
|
Deinstall the xinetd port/package if you have installed it.
|
|
|
|
V. Solution
|
|
|
|
One of the following:
|
|
|
|
1) Upgrade your entire ports collection and rebuild the xinetd port.
|
|
|
|
2) Deinstall the old package and install a new package dated after the
|
|
correction date, obtained from the following directories:
|
|
|
|
[i386]
|
|
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/security/xinetd-2.3.0.tgz
|
|
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/security/xinetd-2.3.0.tgz
|
|
|
|
[alpha]
|
|
Packages are not automatically generated for the alpha architecture at
|
|
this time due to lack of build resources.
|
|
|
|
3) download a new port skeleton for the xinetd port from:
|
|
|
|
http://www.freebsd.org/ports/
|
|
|
|
and use it to rebuild the port.
|
|
|
|
4) Use the portcheckout utility to automate option (3) above. The
|
|
portcheckout port is available in /usr/ports/devel/portcheckout or the
|
|
package can be obtained from:
|
|
|
|
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/devel/portcheckout-2.0.tgz
|
|
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/devel/portcheckout-2.0.tgz
|
|
|
|
-----BEGIN PGP SIGNATURE-----
|
|
Version: GnuPG v1.0.6 (FreeBSD)
|
|
Comment: FreeBSD: The Power To Serve
|
|
|
|
iQCVAwUBO0sPDlUuHi5z0oilAQFOnAQAnzylUXvLsBiT2F5Mfwn94nd/r7nrP1WI
|
|
a7hVwyXSYlfBXRFzsyUQsn1ED/t6mNzDKAiztZ7ZzsIfLxgcy7vFyzWmJSqEx6kk
|
|
pPYzx2KXxB6FXbrSoX1Q4a5WgqWONgFEcG1Vua3nVmApdF0gy8XWinV9I0VWdlVY
|
|
hQjelLjBi1U=
|
|
=umCA
|
|
-----END PGP SIGNATURE-----
|