HTTP ServerWeb server / proxy · Apache

CVE-2007-6750

MEDIUM · 5.0 CVSS v2.0 Published 2011-12-27
Fix available
A fix is available. Upgrade to after 2.2.14 or later.
See remediation →
59/100
Remediation priority · Elevated
High EPSS 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
The Apache HTTP Server 1.x and 2.x allows remote attackers to cause a denial of service (daemon outage) via partial HTTP requests, as demonstrated by Slowloris, related to the lack of the mod_reqtimeout module in versions before 2.2.15.

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

The Apache HTTP Server 1.x and 2.x allows remote attackers to cause a denial of service by sending partial HTTP requests that never complete, as demonstrated by Slowloris. Attackers maintain many open connections by sending headers slowly or incompletely, exhausting the server's connection pool and causing daemon outage. This vulnerability exists because versions before 2.2.15 lack the mod_reqtimeout module which would timeout incomplete requests.

MitigationEnable and configure the mod_reqtimeout module to limit the time allowed for receiving request headers and body, or upgrade to Apache HTTP Server 2.2.15 or later which includes this protection by default.

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
HTTP ServerWeb server / proxy
Affected:<= 2.2.14= 1.0= 1.0.2= 1.0.3= 1.0.5= 1.1= 1.1.1= 1.2= 1.2.4= 1.2.5= 1.2.6= 1.2.9

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. Determine installed Apache HTTP Server version
    Run `httpd -v` or `apache2 -v` to retrieve the server version. On some systems, check `/usr/sbin/httpd -v` or `/usr/sbin/apache2 -v`.
    Affected if The version is 2.2.14 or earlier, or any 1.x version listed in the affected range (1.0, 1.0.2, 1.0.3, 1.0.5, 1.1, 1.1.1, 1.2, 1.2.4, 1.2.5, 1.2.6, 1.2.9).
  2. Verify if mod_reqtimeout module is loaded
    Run `httpd -M` or `apache2 -M` to list compiled-in and loaded modules. Look for `reqtimeout_module` in the output.
    Affected if The module list does not contain mod_reqtimeout (or the module is not present in the output).
  3. Check if mod_reqtimeout is enabled in configuration
    Search for `mod_reqtimeout` or `reqtimeout` in Apache configuration files (typically in `/etc/httpd/conf.d/`, `/etc/apache2/mods-enabled/`, or the main `httpd.conf`/`apache2.conf`).
    Affected if No LoadModule directive for mod_reqtimeout exists, or the module is not enabled in any configuration file.
  4. Inspect mod_reqtimeout configuration settings
    If the module is loaded, check the configuration for Timeout directive values (e.g., `RequestReadTimeout header=20-40,body=20`) in the Apache config files.
    Affected if The mod_reqtimeout module is not configured with timeout limits for headers or body, or no RequestReadTimeout directive is present.

You are affected if your Apache version is 2.2.14 or earlier, or any 1.x version, AND the mod_reqtimeout module is either not loaded or not configured with timeout limits for incomplete requests.

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 a release after 2.2.14
Interim mitigation

Enable and configure the mod_reqtimeout module to limit the time allowed for receiving request headers and body, or upgrade to Apache HTTP Server 2.2.15 or later which includes this protection by default.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-6750 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