Received: (qmail 29442 invoked by uid 2012); 11 May 1999 08:04:32 -0000 Message-Id: <19990511080432.29441.qmail@hyperreal.org> Date: 11 May 1999 08:04:32 -0000 From: Joerg Dorchain Reply-To: dorchain@wirbel.com To: apbugs@hyperreal.org Subject: hardcoded documentroot gives problem with virtual servers X-Send-Pr-Version: 3.2 >Number: 4383 >Category: suexec >Synopsis: hardcoded documentroot gives problem with virtual servers >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue May 11 01:10:00 PDT 1999 >Closed-Date: Fri Jan 07 14:32:31 PST 2000 >Last-Modified: Fri Jan 07 14:32:31 PST 2000 >Originator: dorchain@wirbel.com >Release: 1.3.6 >Organization: >Environment: linux 2.2.7, glibc-2.0.7 >Description: I tried to set up apache for virtual servers when I noticed a problem with the hardcoded documentroot in suexec.c I want to have each virtual server with its own user (and group id) and cgi-bin directory. With to ordinary setup this leads to an "command not in docroot" error. >How-To-Repeat: Try a setup as above >Fix: There are two possibilities which both lead to reduced security: 1. Set the DOCROOT to the least common path (which may be /, i.e. effectivly disables this check) 2. (What I did) Compare the commandpath to the DOCUMENT_ROOT enviroment variable as given by apache. (May be forged easily and effectivly disables this check.) >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: coar State-Changed-When: Fri Jan 7 14:32:30 PST 2000 State-Changed-Why: This is not a bug, but a known facet of suexec's operation. You have already identified the solutions. You can use different users and groups on a per-vhost basis, but the docroot issue remains. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]