From owner-freebsd-security@FreeBSD.ORG Fri May 16 18:47:18 2003 Return-Path: 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 7F55B37B401; Fri, 16 May 2003 18:47:18 -0700 (PDT) Received: from smtp-relay2.barrysworld.com (smtp-relay2.barrysworld.com [213.221.172.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id B754F43FBD; Fri, 16 May 2003 18:47:17 -0700 (PDT) (envelope-from killing@barrysworld.com) Received: from [213.221.181.50] (helo=barrysworld.com) by smtp-relay2.barrysworld.com with esmtp (Exim 4.12) id 19Gqmm-0003HK-00; Sat, 17 May 2003 02:46:56 +0100 Received: from gromit [212.211.104.19] by barrysworld.com with ESMTP (SMTPD32-7.15) id A53A1F99014A; Sat, 17 May 2003 02:49:46 +0100 Message-ID: <001f01c31c1e$7e00e3d0$9f00a8c0@mshome.net> From: "Killing" To: , Date: Sat, 17 May 2003 03:46:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Subject: open and euid security flaw in 5.0-Current? X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2003 01:47:18 -0000 On a FreeBSD 5.0 the behaviour of screen when connecting to other users sessions have changed. Previously: 1. login as userA start a screen as userA and disconnect 2. login as root su - userA "screen -r" 3. result failure as userA cant access the ttyX with such a message Current: 1. login as userA start a screen as userA and disconnect 2. login as root su - userA "screen -r" 3. result failure as userA cant access the ttyX but no message After looking around in screen's code I found that after doing a seteuid( userA ) an open on root's terminal is still succeseding. Surely this is a problem as when running euid userA there should be no access to ruid's files? Steve / K