CVE-2000-0246
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 5.0 does not properly perform ISAPI extension processing if a virtual directory is mapped to a UNC share, which allows remote attackers to read the source code of ASP and other files, aka the "Virtualized UNC Share" 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 5.0 contains a flaw in ISAPI extension processing when virtual directories are mapped to UNC (Universal Naming Convention) network shares. This vulnerability allows remote attackers to retrieve the unprocessed, readable source code of ASP scripts and other server-side files instead of having them executed by the web server.
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= 2.0= 2.5= 4.0= 5.0= 2.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 versionCheck the IIS version by examining the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp or by running 'iisreset /status' or checking the IIS Manager properties. For affected alternatives (MCIS, Proxy Server, Site Server), check their respective version information in Add/Remove Programs or registry.Affected if Version is IIS 4.0, IIS 5.0, MCIS 2.0, MCIS 2.5, Proxy Server 2.0, Site Server 3.0, or Site Server Commerce 3.0
-
Enumerate virtual directories mapped to UNC pathsOpen IIS Manager, expand each website, and inspect the 'Physical Path' column for each virtual directory. Alternatively, use the adsutil.vbs script: cscript adsutil.vbs enum /w3svc/1/ROOT (adjusting the path as needed) and look for entries where 'Path' starts with '\\' (UNC path syntax).Affected if Any virtual directory has its physical path pointing to a UNC share (\\servername\sharename)
-
Verify ISAPI extension handler is enabledIn IIS Manager, go to 'Home Directory' or 'Virtual Directory' configuration and click 'Configuration' to view the Application Mappings. Verify that .asp (and other ISAPI extensions like .asa) are mapped to an ISAPI dll (typically asp.dll). Also check that the 'Script engine' for ASP is enabled in the 'Home Directory' tab under 'Application settings'.Affected if ISAPI extension mapping for .asp exists and is enabled (this is the default configuration)
The environment is affected if running an affected IIS/related product version AND has at least one virtual directory mapped to a UNC share with ISAPI extensions enabled.
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 dataAvoid mapping IIS virtual directories to UNC shares, or if required, ensure proper authentication mechanisms and network segmentation are applied; otherwise, upgrade to a patched IIS version or migrate to a supported platform.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0246 — 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-0246 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