CVE-2000-0025
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 4.0 and Site Server 3.0 allow remote attackers to read source code for ASP files if the file is in a virtual directory whose name includes extensions such as .com, .exe, .sh, .cgi, or .dll, aka the "Virtual Directory Naming" 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 4.0 and Site Server 3.0 contain a vulnerability where ASP source code can be exposed to remote attackers when the files reside in virtual directories whose names contain file extensions such as .com, .exe, .sh, .cgi, or .dll. This allows unauthenticated attackers to view the plaintext source code of ASP files, potentially revealing sensitive information like database credentials, business logic, or other secrets.
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= 4.0= 3.0= 3.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 or Site Server versionCheck the version through IIS Manager (right-click server > Properties > General tab) or by querying the registry key HKLM\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\MajorVersionAffected if Version equals 4.0 for IIS or 3.0 for Site Server (indicates vulnerable version)
-
Enumerate virtual directories with extension-like namesOpen IIS Manager, expand all websites, and list all virtual directories. Look for directory names containing .com, .exe, .sh, .cgi, or .dll (for example: /scripts.exe, /cgi-bin, /scripts.dll, /myshop.com)Affected if Any virtual directory exists with a name containing these file extensions
-
Verify ASP files exist in extension-named virtual directoriesBrowse the identified virtual directories and check if .asp files are present in themAffected if .asp files are stored within virtual directories that have extension-like names
-
Test for source code exposureAttempt to access an ASP file through the vulnerable virtual directory URL (e.g., http://target/scripts.dll/somepage.asp or http://target/virt.com/file.asp) using a web browser or curl. If the server returns plaintext ASP source code instead of executing it, the vulnerability is presentAffected if Accessing .asp files through extension-named virtual directories returns plaintext source code instead of rendered HTML output
You are affected if running IIS 4.0 or Site Server 3.0 AND you have ASP files in virtual directories whose names contain extensions like .com, .exe, .sh, .cgi, or .dll, with those ASP files exposing plaintext source when accessed via the web.
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 dataRename affected virtual directories to remove file extension-like components from their names, or upgrade to patched versions of IIS and Site Server. Restrict network access to legacy IIS 4.0 and Site Server 3.0 systems where possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0025 — 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-0025 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