[16352] in bugtraq
Re: RH 6.1 / 6.2 minicom vulnerability
daemon@ATHENA.MIT.EDU (Fred Souza)
Tue Aug 22 15:25:04 2000
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Message-Id: <20000821213429.A789@torment.secfreak.com>
Date: Mon, 21 Aug 2000 21:34:29 -0300
Reply-To: Fred Souza <cseg@KRONUS.COM.BR>
From: Fred Souza <cseg@KRONUS.COM.BR>
X-To: Michal Zalewski <lcamtuf@DIONE.IDS.PL>
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To: Your message of "Sat, Aug 19 2000 11:43:59 +0200"
<Pine.LNX.4.21.0008191142460.7020-100000@dione.ids.pl>
> On RedHat 6.1 and RedHat 6.2 boxes (I haven't found other distributions
> vulnerable):
>
> @(#)Minicom V1.83.0 (compiled Mar 7 2000)(c) Miquel van Smoorenburg
>
> [lcamtuf@nimue lcamtuf]$ minicom -C foo
> minicom: there is no global configuration file /etc/minirc.dfl
> Ask your sysadm to create one (with minicom -s).
>
> [lcamtuf@nimue lcamtuf]$ ls -l foo
> -rw-rw-r-- 1 lcamtuf uucp 0 Aug 18 12:21 foo
> ^^ ^^^^
>
> Any file can be created anywhere with uucp privledges - it will follow
> symlinks. Not nice on systems running uucp services.
Agreed. I've tested this on FreeBSD 4.1-STABLE, with minicom 1.83.1, and
the file "foo" were created with the correct uid/gid, using the default
umask.
--
This is what you get when you meet someone who has spent most of his/her entire
life, thinking.
