Bugtraq mailing list archives
Re: Hijacking Apache 2 via mod_perl
From: André Malo <nd () perlig de>
Date: Thu, 22 Jan 2004 18:42:28 +0100
* 3APA3A <3APA3A () SECURITY NNOV RU> wrote:
You're right: mod_perl is inside apache memory space and can access any descriptor, so it's impossible to blame apache descriptor is leaked. But you're wrong. mod_perl has access to memory, not perl script. At least, it's possible to store descriptors table and implement check for descriptor in every perl file/socket function inside mod_perl (and mod_php and mod_something) and only allow access to std descriptors and to descriptors open inside same script. The choice is between speed and security.
Then one just writes a perl extension in C. Who's responsible then? Who's responsible if you just write a C module which hijacks the descriptors? Where do you draw the line? nd
Current thread:
- Hijacking Apache 2 via mod_perl Steve Grubb (Jan 21)
- Re: Hijacking Apache 2 via mod_perl Ben Laurie (Jan 22)
- Re[2]: Hijacking Apache 2 via mod_perl 3APA3A (Jan 22)
- Re: Hijacking Apache 2 via mod_perl Ben Laurie (Jan 22)
- Re: Hijacking Apache 2 via mod_perl André Malo (Jan 22)
- Re: Hijacking Apache 2 via mod_perl Steve G (Jan 22)
- Re: Hijacking Apache 2 via mod_perl jon schatz (Jan 23)
- Re: Hijacking Apache 2 via mod_perl Matthew Wakeling (Jan 24)
- Re[2]: Hijacking Apache 2 via mod_perl 3APA3A (Jan 22)
- Re: Re[2]: Hijacking Apache 2 via mod_perl Steve G (Jan 22)
- Re: Hijacking Apache 2 via mod_perl Ben Laurie (Jan 22)