[17560] in bugtraq

home help back first fref pref prev next nref lref last post

Re: vlock vulnerability in RedHat 7.0

daemon@ATHENA.MIT.EDU (Trond Eivind =?iso-8859-1?q?Glomsr)
Wed Nov 8 15:01:22 2000

MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID:  <xuyd7g78s6p.fsf@halden.devel.redhat.com>
Date:         Tue, 7 Nov 2000 15:04:30 -0500
Reply-To: Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= <teg@REDHAT.COM>
From: Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= <teg@REDHAT.COM>
X-To:         Bartlomiej Grzybicki <bgrzybicki@morliny.pl>
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To:  Bartlomiej Grzybicki's message of "Tue, 7 Nov 2000 08:03:40 +0100"

Bartlomiej Grzybicki <bgrzybicki@morliny.pl> writes:

> I've tried to lock all virtual consoles
> in RedHat 7.0 using vlock, which
> is delivered with this release of RedHat.
>
> If user root locks all consoles - it's no problem,
> but if normal user locks consoles then
> anybody can unlock without typing a password.
>
> Try to use it in the following way:
>
> 1. logon as an ordinary user on tty1
> 2. logon as root on tty2
> 3. Type on tty1 vlock -a
> 4. All consoles will be locked.
> 5. When vlock asks for password
> press ENTER and don't release the key
> until you see message 'broken pipe'.
> 6. If you see it all two consoles are unlocked.

How is your system configured? I can't reproduce this.

--
Trond Eivind Glomsrød
Red Hat, Inc.

home help back first fref pref prev next nref lref last post