From owner-freebsd-security  Tue Oct  1 16:37: 4 2002
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id ED1E937B401
	for <security@FreeBSD.ORG>; Tue,  1 Oct 2002 16:37:02 -0700 (PDT)
Received: from lariat.org (lariat.org [63.229.157.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3F9CB43E77
	for <security@FreeBSD.ORG>; Tue,  1 Oct 2002 16:37:02 -0700 (PDT)
	(envelope-from brett@lariat.org)
Received: from mustang.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2])
	by lariat.org (8.9.3/8.9.3) with ESMTP id RAA24158;
	Tue, 1 Oct 2002 17:36:55 -0600 (MDT)
X-message-flag: Warning! Use of Microsoft Outlook is dangerous and makes your system susceptible to Internet worms.
Message-Id: <4.3.2.7.2.20021001173317.034cfe10@localhost>
X-Sender: brett@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 01 Oct 2002 17:36:51 -0600
To: "f.johan.beisser" <jan@caustic.org>
From: Brett Glass <brett@lariat.org>
Subject: Re: tar/security best practice (was Re: RE: Is FreeBSD's tar  
  susceptible to this?)
Cc: security@FreeBSD.ORG
In-Reply-To: <20021001162006.C67581-100000@pogo.caustic.org>
References: <4.3.2.7.2.20021001170815.0345ab20@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-security.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-security>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-security>
X-Loop: FreeBSD.org

At 05:25 PM 10/1/2002, f.johan.beisser wrote:

>sadly, i have to admit that won't work, not without adding in the leading
>"/". remember that "~" is expanded to "/home/$USER". 

I was using the ~ notation as a shorthand. The point is that if you can
get at a user's .forward file, that's sufficient to run code as him/her.
There are lots of other clever ways, too; that's just the first
example that came to mind.

Rather than give someone the opportunity to find a clever exploit, I think
we'd best just close the hole. ;-)

--Brett


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message