Hi,
We have received the following vulnerability report:
http://www.securityfocus.com/bid/23192/info
I read the changes for the mod_perl versions but did not find anything really
clear. We are using mod_perl version 2.0.3 compiled for Suse linux enterprise
server 10 sp2 used with apache 2.0
On Wed, May 6, 2009 at 7:40 AM, Francois Pernet francois.per...@idsa.chwrote:
Hi,
We have received the following vulnerability report:
http://www.securityfocus.com/bid/23192/info
I read the changes for the mod_perl versions but did not find anything
really clear. We are using mod_perl
For mod_perl 2 users, this only affects you if you use
ModPerl::PerlRun or ModPerl::Registry.
- Perrin
On Wed, May 6, 2009 at 7:40 AM, Francois Pernet francois.per...@idsa.ch wrote:
Hi,
We have received the following vulnerability report:
http://www.securityfocus.com/bid/23192/info
I read
Update - I fat fingered the CVE number in this email body previously
(but it was correct in the subject).
The correct vulnerability reference number is CVE-2009-0796.
On Wed, Apr 1, 2009 at 2:58 PM, Fred Moyer f...@redhotpenguin.com wrote:
mod_perl lists,
A specific vulnerability [CVE-2009
mod_perl lists,
A specific vulnerability [CVE-2009-0795] in Apache::Status and
Apache2::Status has been discovered which may affect the security of
your mod_perl installation. Running Apache::Status on a public server
with no protection has always been a bad idea though, vulnerability