HTTP ServerWeb server / proxy · Apache
CVE-2000-1206
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 · uneditedVulnerability in Apache httpd before 1.3.11, when configured for mass virtual hosting using mod_rewrite, or mod_vhost_alias in Apache 1.3.9, allows remote attackers to retrieve arbitrary files.
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 confidencePath traversal vulnerability in Apache httpd versions before 1.3.11 when configured for mass virtual hosting using mod_rewrite or mod_vhost_alias. Attackers can use directory traversal sequences (e.g., ../../../) to access arbitrary files outside the intended web root through the mass virtual hosting rewrite rules.
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
= 1.3.9= 1.3.10CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Determine installed Apache versionRun 'httpd -v' or 'apachectl -v' to display the server versionAffected if Version is 1.3.9 or 1.3.10
-
Check if mod_rewrite is enabledRun 'httpd -M' to list compiled-in modules, or search config files for 'LoadModule rewrite_module' and rewrite directives like RewriteRule with variable patternsAffected if mod_rewrite is loaded and configured for mass virtual hosting (using variable captures like %{HTTP_HOST})
-
Check if mod_vhost_alias is enabledRun 'httpd -M' to list modules, or search config files for 'LoadModule vhost_alias_module' and directives like VirtualDocumentRootAffected if mod_vhost_alias is enabled for mass virtual hosting
-
Inspect mass virtual hosting rewrite rulesReview Apache config files for RewriteRule patterns that use %{HTTP_HOST} or similar variables in the substitution string without proper sanitizationAffected if Rewrite rules perform mass virtual hosting transformations without blocking directory traversal sequences (../)
You are affected if you run Apache 1.3.9 or 1.3.10 with mod_rewrite or mod_vhost_alias configured for mass virtual hosting, and your rewrite rules allow directory traversal sequences in URLs.
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 to Apache httpd 1.3.11 or later which contains the fix. For systems that cannot be upgraded immediately, disable or properly restrict mod_rewrite and mod_vhost_alias configurations, and implement input validation to reject path traversal sequences in URLs.
Fix this in HTTP Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-1206 — 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-2000-1206 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