Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 May 2000 11:34:03 +0900
From:      sen_ml@eccosys.com
To:        freebsd-security@FreeBSD.ORG
Subject:   Re: QPOPPER: Remote gid mail exploit
Message-ID:  <20000530113403A.1001@eccosys.com>
In-Reply-To: <20000529161403.H19887@vuurwerk.nl>
References:  <Pine.BSF.4.21.0005241633020.7700-100000@mercury.jorsm.com> <20000525160410I.1001@eccosys.com> <20000529161403.H19887@vuurwerk.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
From: Peter van Dijk <petervd@vuurwerk.nl>
Subject: Re: QPOPPER: Remote gid mail exploit
Date: Mon, 29 May 2000 16:14:03 +0200
Message-ID: <20000529161403.H19887@vuurwerk.nl>

> On Thu, May 25, 2000 at 04:04:10PM +0900, sen_ml@eccosys.com wrote:
> [snip]
>
> > while patching and restarting a qpopper server locally, i started
> > wondering...how much of a problem is this on a freebsd system where
> > /var/mail or /var/spool/mail is not setgid mail?
> 
> As with the IMAP exploit, this will give people a shell, which they usually
> didn't have beforehand, when they are just popusers.

since the problem has to w/ a pop command that's issued after
successful authentication, if the user already has shell access, then
there isn't anything to worry about, is there?  or is the shell
running as some other user?


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000530113403A.1001>