Re: Apache (httpd) + Persistant Perl (ModPerl/SpeedyCGI) + User Based Processes (SuExec) + Chroot

Just two quick comments:

1. chroot is not very effective as a security measure. For instance, see How to break out of a chroot() jail.

2. I'd bounce these ideas off of the modperl mailing list (modperl@perl.apache.org).

Comment on Re: Apache (httpd) + Persistant Perl (ModPerl/SpeedyCGI) + User Based Processes (SuExec) + Chroot Select or Download Code

Replies are listed 'Best First'.
Re^2: Apache (httpd) + Persistant Perl (ModPerl/SpeedyCGI) + User Based Processes (SuExec) + Chroot by zxViperxz (Acolyte) on Jun 24, 2008 at 00:35 UTC
Thanks for the comments. The exploit you pointed out, requires a user to have root privledges to be able to break out of the Jail. The only point where root priveldges are used is when suExec performs the user change and the chroot which is done via a SUID bit. SuExec prevents changing to a user with a GID/UID < 100, so as long as suExec is secure (which, due to it's simplicity it ususally is), that exploit should be blocked off. As for the modperl users tip, I shall go post this question there now. James Austin.	[reply]

Replies are listed 'Best First'.