dbcve.org
Mod PerlApplication · Apache

CVE-2007-1349

MEDIUM · 5.0 CVSS v2.0 Published 2007-03-30
Fix available
A fix is available. Upgrade to 1.30 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PerlRun.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 expression, which allows remote attackers to cause a denial of service (resource consumption) via a crafted URI.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

mod_perl's PerlRun.pm (before 1.30) and RegistryCooker.pm (2.x) fail to escape PATH_INFO before using it in a regular expression, allowing crafted URIs to trigger catastrophic backtracking (ReDoS) and cause denial of service through excessive resource consumption.

MitigationUpgrade to mod_perl 1.30 or later (1.x) or apply all available patches for mod_perl 2.x; alternatively, deploy Apache-level request filtering to reject malformed or excessively long PATH_INFO strings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mod PerlApplication
Affected:< 1.30>= 2.0.0, <= 2.0.11
Ubuntu LinuxOperating system
Affected:= 6.06= 6.10= 7.04
SatelliteApplication
Affected:= 5.1
Enterprise Linux DesktopOperating system
Affected:= 3.0= 4.0= 5.0
Enterprise Linux EusOperating system
Affected:= 4.5
Enterprise Linux ServerOperating system
Affected:= 3.0= 4.0= 5.0
Enterprise Linux WorkstationOperating system
Affected:= 3.0= 4.0= 5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed mod_perl version
    Run 'perl -Mmod_perl -e "print $mod_perl::VERSION"' or check Apache error log for mod_perl version at startup, or run 'httpd -l' to list compiled modules
    Affected if Version is below 1.30 for 1.x series, or between 2.0.0 and 2.0.11 for 2.x series
  2. Verify mod_perl is loaded in Apache
    Check Apache configuration files (httpd.conf, apache2.conf) for 'LoadModule perl_module' or run 'httpd -M' to list loaded modules
    Affected if mod_perl module is loaded and active
  3. Confirm PerlRun or RegistryCooker handler is in use
    Search Apache config files for 'PerlHandler Apache::PerlRun' or 'PerlHandler Apache::Registry' or 'PerlResponseHandler Apache::PerlRun' or 'PerlResponseHandler Apache::Registry'
    Affected if Either PerlRun or RegistryCooker handler is configured as a response or content handler
  4. Check if application uses PATH_INFO
    Review application scripts or Apache config for RewriteRule patterns handling PATH_INFO, or check access logs for requests containing PATH segments after the script name (e.g., /script.pl/extra/path)
    Affected if The application processes PATH_INFO via mod_perl handlers

You are affected if mod_perl version is below 1.30 (1.x) or between 2.0.0 and 2.0.11 (2.x), AND the PerlRun or RegistryCooker handler is configured, AND your application uses PATH_INFO which could trigger the unescaped regex.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.30 or later
Fixed in 1.30
Interim mitigation

Upgrade to mod_perl 1.30 or later (1.x) or apply all available patches for mod_perl 2.x; alternatively, deploy Apache-level request filtering to reject malformed or excessively long PATH_INFO strings.

Fix this in Mod Perl Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1349 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-1349 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data