CVE-2000-0778
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 · uneditedIIS 5.0 allows remote attackers to obtain source code for .ASP files and other scripts via an HTTP GET request with a "Translate: f" header, aka the "Specialized Header" vulnerability.
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 confidenceIIS 5.0 contains a vulnerability where sending an HTTP GET request with the 'Translate: f' header causes the server to return the unexecuted source code of .ASP files and other scripts instead of processing them. This is a WebDAV-related header handling flaw that enables information disclosure of sensitive application source code.
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= 5.0CVSS 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.
-
Identify IIS versionCheck the server's HTTP response headers or use the command 'iisweb.vbs' script (if available) or check the Windows version info for IIS installation. Look for 'Server: Microsoft-IIS/5.0' in HTTP responses.Affected if The server responds with 'Microsoft-IIS/5.0' in the Server header, confirming it is running IIS 5.0
-
Confirm WebDAV is availableSend an OPTIONS HTTP request to the server root (OPTIONS / HTTP/1.1) and check for WebDAV methods like PROPFIND, DELETE, MOVE in the Allow header.Affected if The server returns WebDAV methods in the Allow header, indicating WebDAV is enabled and the Translate header will be processed
-
Test for Translate header vulnerabilitySend a GET request for an existing .asp file with the header 'Translate: f' (e.g., GET /page.asp HTTP/1.1\r\nHost: target\r\nTranslate: f\r\n) and examine if the response contains unexecuted ASP source code instead of processed output.Affected if The response contains raw ASP source code (look for <% or %> tags or other VBScript/JScript code) rather than the normal processed HTML output
-
Verify file exists before testingFirst confirm the target .asp file exists by sending a normal GET request without the Translate header and verifying a 200 OK response.Affected if The .asp file returns 200 OK normally but returns source code when the Translate: f header is added
The server is affected if it runs IIS 5.0 with WebDAV enabled and responds with unexecuted ASP source code when receiving a GET request with the 'Translate: f' header.
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 dataBlock or filter the 'Translate' HTTP header at the web server or firewall level, or upgrade from IIS 5.0 to a supported version as IIS 5.0 is obsolete and no longer receives security updates.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0778 — 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-0778 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