From owner-doc-jp@jp.freebsd.org  Sat May 27 13:15:15 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id NAA90013;
	Sat, 27 May 2000 13:15:15 +0900 (JST)
	(envelope-from owner-doc-jp@jp.FreeBSD.org)
Received: from iris.dti.ne.jp (PPP43.sendai-ap2.dti.ne.jp [210.170.212.43])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id NAA89956
	for <doc-jp@jp.freebsd.org>; Sat, 27 May 2000 13:15:13 +0900 (JST)
	(envelope-from dais@iris.dti.ne.jp)
Received: (from dais@localhost)
	by iris.dti.ne.jp (8.9.3/8.8.8) id NAA10586;
	Sat, 27 May 2000 13:14:00 +0900 (JST)
	(envelope-from dais)
Date: Sat, 27 May 2000 13:14:00 +0900 (JST)
Message-Id: <200005270414.NAA10586@iris.dti.ne.jp>
To: doc-jp@jp.freebsd.org
In-Reply-To: <20000526174039.514AE37BF77@hub.freebsd.org>
References: <20000526174039.514AE37BF77@hub.freebsd.org>
From: dais@iris.dti.ne.jp (Daisuke Higashi)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-2022-JP
X-Mailer: mnews [version 1.21PL5] 1999-04/04(Sun)
Reply-To: doc-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: doc-jp 7413
Subject: [doc-jp 7413] Re: ANNOUNCE: FreeBSD Security Advisory: FreeBSD-SA-00:20.krb5
Errors-To: owner-doc-jp@jp.freebsd.org
Sender: owner-doc-jp@jp.freebsd.org
X-Originator: dais@iris.dti.ne.jp

$BEl$G$9!#$H$$$&$o$1$G!"(BFreeBSD-SA-00:20.krb5 $B$b!#(B

----------------

$B$3$N%a!<%k$O!"(Bannounce-jp $B$KN.$l$?(B 

Subject: ANNOUNCE: FreeBSD Security Advisory: FreeBSD-SA-00:20.krb5
From: FreeBSD Security Officer <security-officer@freebsd.org>
Date: Fri, 26 May 2000 10:40:39 -0700 (PDT)
Message-Id: <20000526174039.514AE37BF77@hub.freebsd.org>
X-Sequence: announce-jp 449

$B$rF|K\8lLu$7$?$b$N$G$9!#(B

$B86J8$O(B PGP $B=pL>$5$l$F$$$^$9$,!"$3$NF|K\8lLu$O(B PGP $B=pL>$5$l$F$$$^$;$s(B. 
$B%Q%C%AEy$NFbMF$,2~cb$5$l$F$$$J$$$3$H$r3NG'$9$k$?$a$K(B PGP $B$N%A%'%C%/$r(B
$B9T$J$&$K$O!"86J8$r;2>H$7$F$/$@$5$$(B. 

$BF|K\8lLu$O(B FreeBSD $BF|K\8l%I%-%e%a%s%F!<%7%g%s%W%m%8%'%/%H(B(doc-jp)$B$,;29M$N(B
$B$?$a$KDs6!$9$k$b$N$G!"(Bdoc-jp $B$O(B $B$=$NFbMF$K$D$$$F$$$+$J$kJ]>Z$b$$$?$7$^$;$s(B.
$BF|K\8lLu$K$D$$$F$N$*Ld$$9g$o$;$O(B doc-jp@jp.freebsd.org $B$^$G$*4j$$$7$^$9(B.


=============================================================================
FreeBSD-SA-00:20                                           Security Advisory
                                                                FreeBSD, Inc.

$B%H%T%C%/(B:        krb5 port $B$K4^$^$l$k%j%b!<%H$*$h$S%m!<%+%k$K$*$1$k(B
                 root $B8"8BC%<h$N4m81@-(B
$BJ,N`(B:            ports
$B%b%8%e!<%k(B:      krb5
$B9pCNF|(B:          2000-05-26
$B%/%l%8%C%H(B:      Jeffrey I. Schiller <jis@MIT.EDU>
$B1F6AHO0O(B:        $B=$@5F|0JA0$N(B ports $B%3%l%/%7%g%s(B
$B=$@5F|(B:          2000-05-17
$B%Y%s%@$NBP1~(B:    $B%Q%C%A$N%j%j!<%9(B
FreeBSD$B$K8GM-$+(B: NO

I.   $BGX7J(B - Background

MIT Kerberos 5 is an implementation of the Kerberos 5 protocol which
is available in the FreeBSD ports collection as the security/krb5
port. FreeBSD also includes separately-developed Kerberos 4 and 5
implementations from KTH, which are optionally installed as part of
the base system (KTH Heimdal, the Kerberos 5 implementation, is
currently considered "experimental" software).

MIT Kerberos 5 $B$O(B security/krb5 $B$H$7$F(B FreeBSD $B$N(B ports
$B%3%l%/%7%g%s$+$iMxMQ$G$-$k(B Kerberos 5 $B%W%m%H%3%k$N<BAu$G$9!#(B
FreeBSD $B$O$^$?!"JL$K3+H/$5$l$?(B KTH $B$K$h$k(B Kerberos 4 $B$*$h$S(B 5 $B$N(B
$B<BAu$r4^$s$G$*$j!"%Y!<%9%7%9%F%`(B (base system) $B$N0lItJ,$H$7$F(B
$BG$0U$K%$%s%9%H!<%k$5$l$^$9!#(B(Kerberos 5 $B$N<BAu$G$"$k(B KTH Heimdal $B$O!"(B
$B8=:_!V<B83E*$J(B(experimental)$B!W%=%U%H%&%'%"$H9M$($i$l$F$$$^$9!#(B)

II.  $BLdBj$N>\:Y(B - Problem Description

The MIT Kerberos 5 port, versions 1.1.1 and earlier, contains several
remote and local buffer overflows which can lead to root compromise.

Note that the implementations of Kerberos shipped in the FreeBSD base
system are separately-developed software to MIT Kerberos and are
believed not to be vulnerable to these problems.

MIT Kerberos 5 $B$N(B port $B$O!"(B1.1.1 $B$*$h$S$=$l0JA0$N%P!<%8%g%s(B
$B$K$D$$$F!"%k!<%H8"8B$NC%<h$K$D$J$,$k%j%b!<%H$*$h$S%m!<%+%k$N(B
$B$$$/$D$+$N%P%C%U%!%*!<%P%U%m!<$N2DG=@-$,$"$j$^$9!#(B

FreeBSD $B$N(B $B%Y!<%9(B (base) $B%7%9%F%`$H$H$b$K=P2Y$5$l$F$$$k(B
Kerberos $B$N<BAu$O(B MIT Kerberos $B$H$OJL$K3+H/$5$l$F$$$k$b$N$G!"(B
$B$3$l$i$NLdBj$KBP$7$F@H<e$G$O$J$$$H9M$($i$l$F$$$^$9!#(B

However, a very old release of FreeBSD dating from 1997 (FreeBSD
2.2.5) did ship with a closely MIT-derived Kerberos implementation
("eBones") and may be vulnerable to attacks of the kind described
here. Any users still using FreeBSD 2.2.5 and who have installed the
optional Kerberos distribution are urged to upgrade to 2.2.8-STABLE or
later. Note however that FreeBSD 2.x is no longer an officially
supported version, nor are security fixes always provided.

$B$7$+$7$J$,$i!"(B1997 $BG/0J9_$N!"Hs>o$K8E$$(B FreeBSD $B$N%j%j!<%9(B
(FreeBSD 2.2.5) $B$O!"(BMIT $BM3Mh$N(B Kerberos $B$K6a$$<BAu$H$H$b$K(B
$B=P2Y$5$l$F$*$j!"$*$=$i$/$3$3$K=q$+$l$F$$$kF1<o$N967b$KBP$7$F(B
$B@H<e$G$7$g$&!#(BFreeBSD 2.2.5 $B$r$$$^$@$K;HMQ$7!"%*%W%7%g%s$N(B
Kerberos $B$NG[I[$r%$%s%9%H!<%k$7$F$$$k%f!<%6$O!"(B2.2.8-STABLE $B$"$k$$$O(B
$B$=$l0J9_$N$b$N$K%"%C%W%0%l!<%I$9$k$3$H$,4+$a$i$l$^$9!#(B
$B$7$+$7!"(BFreeBSD 2.x $B$O!"$b$O$d8x<0$K$O%5%]!<%H$5$l$J$$%P!<%8%g%s$G!"(B
$B%;%-%e%j%F%#$K4X$9$k=$@5$bDs6!$5$l$J$$$3$H$KCm0U$7$F$/$@$5$$!#(B

The krb5 port is not installed by default, nor is it "part of FreeBSD"
as such: it is part of the FreeBSD ports collection, which contains
nearly 3300 third-party applications in a ready-to-install format. The
ports collection shipped with FreeBSD 4.0 contains this problem since
it was discovered after the release.

$B%G%U%)%k%H$G$O(B krb5 $B$N(B port $B$O%$%s%9%H!<%k$5$l$^$;$s$7!"(B
$B$=$l<+BN$O!V(BFreeBSD $B$N0lIt!W$G$O$"$j$^$;$s(B: $B$3$l$O(B FreeBSD $B$N(B
ports $B%3%l%/%7%g%s$N0lIt$G!"$=$l$i$O$9$0$K%$%s%9%H!<%k2DG=$J7A<0$N(B
$BLs(B 3300 $B<oN`$N%5!<%I%Q!<%F%#@=%"%W%j%1!<%7%g%s$G$9!#(B
FreeBSD 4.0 $B$H$H$b$K=P2Y$5$l$?(B ports $B%3%l%/%7%g%s$O!"(B
$B%j%j!<%98e$KLdBj$,8+$D$+$C$?$?$a$K$3$NLdBj$r4^$s$G$$$^$9!#(B

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.

FreeBSD $B$G$O(B, $B$3$N$h$&$J%5!<%I%Q!<%F%#@=%"%W%j%1!<%7%g%s$N%;%-%e%j%F%#LdBj$K(B
$BBP$7$F!"FC$K2?$+$r<gD%$9$k$3$H$O$"$j$^$;$s(B ($BLuCm(B: Ports Collection $B$KF~$C$F(B
$B$$$k$+$i$H$$$C$F!"(BFreeBSD $B$N3+H/<T$?$A$,$=$N%"%W%j%1!<%7%g%s$,0BA4$G$"$k$H(B
$BI>2A$7$?$o$1$G$O$"$j$^$;$s(B)$B!#$?$@$7!"%;%-%e%j%F%#LdBj$KBP$7$FBg$-$J1F6A$r(B
$B;}$D$h$&$J(B ports $B$KBP$9$k%;%-%e%j%F%#4F::$rDs6!$9$Y$/!"8=:_EXNOCf$G$9(B. 

III. $B1F6AHO0O(B - Impact

Local or remote users can obtain root access on the system running krb5.

If you have not chosen to install the krb5 port, then your system is
not vulnerable to this problem.

krb5 $B$r2TF/$7$F$$$k%7%9%F%`>e$G!"%m!<%+%k$"$k$$$O%j%b!<%H$N(B
$B%f!<%6$,(B root $B8"8B$N%"%/%;%9$rF@$k$3$H$,2DG=$G$9!#(B

krb5 $B$N(B port $B$r%$%s%9%H!<%k$9$k$3$H$rA*Br$7$F$$$J$1$l$P!"(B
$B$"$J$?$N%7%9%F%`$O$3$NLdBj$KBP$9$k@H<e@-$O$"$j$^$;$s!#(B

IV.  $BBP1~:v(B - Workaround

Due to the nature of the vulnerability there are several programs and
network services which are affected. If recompiling the port is not
practical, please see the MIT Kerberos advisory for suggested
workarounds (including the disabling or adjustment of services and
removal of setuid permissions on vulnerable binaries). The advisory
can be found at the following location:

http://web.mit.edu/kerberos/www/advisories/krb4buf.txt

$B$3$N@H<e@-$N@-<A$N$?$a!"$$$/$D$+$N%W%m%0%i%`$d(B
$B%M%C%H%o!<%/%5!<%S%9$,1F6A$r<u$1$^$9!#(Bports $B$r:F%3%s%Q%$%k(B
$B$9$k$3$H$,8=<BE*$G$J$1$l$P!"Ds0F$5$l$F$$$kBP1~:v(B
($B%5!<%S%9$NDd;_!&=$@5$*$h$S!"LdBj$N$"$k%P%$%J%j$N(B setuid $B%Q!<%_%C%7%g%s$N(B
$B=|5n$r4^$s$G$$$^$9(B)$B$K4X$9$k(B MIT Kerberos $B$N9pCN$r;2>H$7$F$/$@$5$$!#(B
$B9pCN$O<!$N>l=j$GF@$i$l$^$9!#(B

http://web.mit.edu/kerberos/www/advisories/krb4buf.txt

V.   $B=$@5=hCV(B - Solution  

1) Upgrade your entire ports collection and rebuild the krb5 port. A
package is not provided for this port for export control reasons.

2) download a new port skeleton for the krb5 port from:

http://www.freebsd.org/ports/

and use it to rebuild the port.

3) 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/packages/devel/portcheckout-1.0.tgz

1) ports $B%3%l%/%7%g%sA4BN$r%"%C%W%0%l!<%I$7!"(Bkrb5 $B$N(B port $B$r(B
$B%j%S%k%I$7$F$/$@$5$$!#M"=P5,@)$N$?$a(B package $B$ODs6!$5$l$F$$$^$;$s!#(B

2) krb5 port $B$rMxMQ$9$k?7$7$$(B port $B%9%1%k%H%s$r<!$N>l=j$+$i(B
$B%@%&%s%m!<%I$7!"(Bport $B$r%j%S%k%I$7$F$/$@$5$$!#(B

http://www.freebsd.org/ports/

3) $B>e$G%*%W%7%g%s(B (3) $B$r<+F02=$9$k$?$a$N%f!<%F%#%j%F%#$G$"$k(B
portcheckout $B$r;H$C$F$/$@$5$$!#(Bportcheckout  $B$N(B port $B$O(B
/usr/ports/devel/portcheckout $B$K$"$j$^$9!#(Bpackage $B$,(B

ftp://ftp.freebsd.org/pub/FreeBSD/ports/packages/devel/portcheckout-1.0.tgz

$B$+$iF~<j2DG=$G$9!#(B

