Description
mod_perl 2.0 through 2.0.10 allows attackers to execute arbitrary Perl code by placing it in a user-owned .htaccess file, because (contrary to the documentation) there is no configuration option that permits Perl code for the administrator's control of HTTP request processing without also permitting unprivileged users to run Perl code in the context of the user account that runs Apache HTTP Server processes.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
n/a mod_perl 2.0 through 2.0.10
mod_perl 2.0 through 2.0.10affected
References
- https://lists.debian.org/debian-lts-announce/2018/09/msg00018.html ↗
- http://www.securityfocus.com/bid/105195 ↗
- https://usn.ubuntu.com/3825-1/ ↗
- https://bugs.debian.org/644169 ↗
- https://access.redhat.com/errata/RHSA-2018:2826 ↗
- https://mail-archives.apache.org/mod_mbox/perl-modperl/201110.mbox/raw/%3C20111004084343.GA21290%40ktnx.net%3E ↗
- https://access.redhat.com/errata/RHSA-2018:2825 ↗
- https://access.redhat.com/errata/RHSA-2018:2737 ↗
- https://usn.ubuntu.com/3825-2/ ↗
- https://lists.apache.org/thread.html/c8ebe8aad147a3ad2e7b0e8b2da45263171ab5d0fc7f8c100feaa94d%40%3Cmodperl-cvs.perl.apache.org%3E ↗
- http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00063.html ↗
- http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00065.html ↗