full-disclosure - AW: securing php

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <DF79BE12AF8DD344B107D0D03621E5750ED9C2@kermit.corp.hansenet.com>
From: vogt at hansenet.com (vogt@...senet.com)
Subject: AW: securing php

> I have a friend that owns a web hosting company and recently 
> he asked me to check up on his security ... I found that PHP 
> scripts could access, modify, etc. anything on the drive. Of 
> course, this is because PHP was invoked by apache, which is 
> being run as a root user (Administrator, he runs apache on 
> win2k3 for some odd reason) but I do not know the remedy. How 
> could he set up his apache/PHP so that only the users of his 
> web hosting service could "do stuff" to their own web 
> directories. I know I am not explaining this well, but I 
> think you get the picture :) I also know there is a simple 
> solution to this, I googled it though and I couldn't find it.

There is no good solution.

You an enable PHP's "Safe Mode", which goes a long way to
closing these holes, but it's not a 100% solution.


Tom