HTTP ServerWeb server / proxy · Apache
CVE-2007-0086
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 · uneditedThe Apache HTTP Server, when accessed through a TCP connection with a large window size, allows remote attackers to cause a denial of service (network bandwidth consumption) via a Range header that specifies multiple copies of the same fragment. NOTE: the severity of this issue has been disputed by third parties, who state that the large window size required by the attack is not normally supported or configured by the server, or that a DDoS-style attack would accomplish the same goal
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 · moderate confidenceApache HTTP Server contains a denial-of-service vulnerability where specially crafted HTTP Range headers specifying duplicate fragments, when used with TCP connections supporting large window sizes, can cause excessive bandwidth consumption. The attack exploits how Apache processes Range header requests by specifying multiple copies of the same byte range.
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
all versionsCVSS 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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Apache HTTP Server is runningCheck for httpd or apache2 processes using 'ps aux | grep -E "httpd|apache2"' or check if port 80/443 is listening using 'netstat -tlnp | grep -E ":80|:443"'Affected if Apache HTTP Server is running and accessible on the network
-
Determine installed Apache versionRun 'httpd -v' (RHEL/CentOS) or 'apache2 -v' (Debian/Ubuntu) or check the server banner via 'curl -I http://localhost'Affected if Any version of Apache HTTP Server is installed (the vulnerability affects all versions)
-
Confirm Range header processing is enabledSend a request with a Range header to the server: 'curl -H "Range: bytes=0-10" http://localhost/' and verify a 206 Partial Content response is returnedAffected if The server responds with 206 Partial Content, indicating Range header processing is active and the server could be exploited
-
Check TCP window size configuration (optional context)Review the server's network configuration and TCP settings. Large receive/send window sizes (e.g., above default) can be verified via 'sysctl net.ipv4.tcp_rmem' and 'sysctl net.ipv4.tcp_wmem'Affected if TCP window scaling is enabled and large values are configured, which would make the attack more effective
If Apache HTTP Server is running with Range header processing enabled (default), the environment is affected by this vulnerability regardless of version, especially when TCP window scaling is active.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Apache HTTP Server to a patched version or implement Range header request limits/rate limiting at the web application firewall or server level to mitigate this vulnerability.
Fix this in HTTP Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0086 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0086 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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