Skip to content
Noroxi
CVE-2011-2767· NVD / CVE Program· CNA debian

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

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.

CriticalCVSS 9.8 · v3.0—No exploit Fix available
Published
Aug 26, 2018
Updated
Jun 16, 2026
EPSS
8.9% · 95th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

42

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 8.9%

Affected systems

VendorProduct
apachemod perl
debiandebian linux
redhatenterprise linux
redhatenterprise linux desktop
redhatenterprise linux server
redhatenterprise linux workstation
canonicalubuntu linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache mod perl2.0.0 and later · up to 2.0.10 inclusive
  • canonical ubuntu linux12.04
  • canonical ubuntu linux14.04
  • canonical ubuntu linux16.04
  • canonical ubuntu linux18.04
  • canonical ubuntu linux18.10
  • debian debian linux8.0
  • redhat enterprise linux6.0
  • redhat enterprise linux6.7
  • redhat enterprise linux7.0
  • redhat enterprise linux7.3
  • redhat enterprise linux7.4
  • redhat enterprise linux7.5
  • redhat enterprise linux7.6
  • redhat enterprise linux desktop6.0
  • redhat enterprise linux server6.0
  • redhat enterprise linux workstation6.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (debian). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a mod_perl 2.0 through 2.0.10

    • mod_perl 2.0 through 2.0.10affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12libapache2-mod-perl2before 2.0.10-32.0.10-3
Debian:8libapache2-mod-perl2before 2.0.9~1624218-2+deb8u32.0.9~1624218-2+deb8u3
openSUSE:Leap 15.0apache2-mod_perlbefore 2.0.11-lp151.3.3.12.0.11-lp151.3.3.1
openSUSE:Tumbleweedapache2-mod_perlbefore 2.0.11-2.122.0.11-2.12
Red Hat:enterprise_linux:6::clientmod_perlbefore 0:2.0.4-12.el6_100:2.0.4-12.el6_10
Red Hat:enterprise_linux:6::clientmod_perl-debuginfobefore 0:2.0.4-12.el6_100:2.0.4-12.el6_10
Red Hat:enterprise_linux:6::clientmod_perl-develbefore 0:2.0.4-12.el6_100:2.0.4-12.el6_10
Red Hat:rhel_software_collections:3::el6rh-perl524-mod_perlbefore 0:2.0.9-10.el60:2.0.9-10.el6
Red Hat:rhel_software_collections:3::el6rh-perl524-mod_perl-debuginfobefore 0:2.0.9-10.el60:2.0.9-10.el6
Red Hat:rhel_software_collections:3::el6rh-perl524-mod_perl-develbefore 0:2.0.9-10.el60:2.0.9-10.el6
Red Hat:rhel_software_collections:3::el7rh-perl524-mod_perlbefore 0:2.0.9-10.el70:2.0.9-10.el7
Red Hat:rhel_software_collections:3::el7rh-perl524-mod_perl-debuginfobefore 0:2.0.9-10.el70:2.0.9-10.el7
Red Hat:rhel_software_collections:3::el7rh-perl524-mod_perl-develbefore 0:2.0.9-10.el70:2.0.9-10.el7
Red Hat:rhel_software_collections:3::el7rh-perl526-mod_perlbefore 0:2.0.10-10.el70:2.0.10-10.el7
Red Hat:rhel_software_collections:3::el7rh-perl526-mod_perl-debuginfobefore 0:2.0.10-10.el70:2.0.10-10.el7
Red Hat:rhel_software_collections:3::el7rh-perl526-mod_perl-develbefore 0:2.0.10-10.el70:2.0.10-10.el7
SUSE:Linux Enterprise Point of Sale 11 SP3apache2-mod_perlbefore 2.0.4-40.63.3.32.0.4-40.63.3.3
SUSE:Linux Enterprise Software Development Kit 12 SP4apache2-mod_perlbefore 2.0.8-13.5.12.0.8-13.5.1
SUSE:Package Hub 15apache2-mod_perlbefore 2.0.11-bp151.4.3.12.0.11-bp151.4.3.1

Other highest-scoring records for the same primary product.

  • CVE-2007-1349PerlRun.pm in Apache mod_perl before 1.30, and RegistryCooker.pm in mod_perl 2.x, does not properly escape PATH_INFO before use in a regular
    23Monitor
  • CVE-2009-0796Cross-site scripting (XSS) vulnerability in Status.pm in Apache::Status and Apache2::Status in mod_perl1 and mod_perl2 for the Apache HTTP S
    19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:libapache2-mod-perl22.0.10-3 · Debian:12Package registry (OSV)
opensuse:apache2-mod_perl2.0.11-lp151.3.3.1 · openSUSE:Leap 15.0Package registry (OSV)
red hat:mod_perl0:2.0.4-12.el6_10 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:mod_perl-debuginfo0:2.0.4-12.el6_10 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:mod_perl-devel0:2.0.4-12.el6_10 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:rh-perl524-mod_perl0:2.0.9-10.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-perl524-mod_perl-debuginfo0:2.0.9-10.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-perl524-mod_perl-devel0:2.0.9-10.el6 · Red Hat:rhel_software_collections:3::el6Package registry (OSV)
red hat:rh-perl526-mod_perl0:2.0.10-10.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-perl526-mod_perl-debuginfo0:2.0.10-10.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-perl526-mod_perl-devel0:2.0.10-10.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
suse:apache2-mod_perl2.0.8-13.5.1 · SUSE:Linux Enterprise Software Development Kit 12 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records