CVE-2000-0413
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 shtml.exe program in the FrontPage extensions package of IIS 4.0 and 5.0 allows remote attackers to determine the physical path of HTML, HTM, ASP, and SHTML files by requesting a file that does not exist, which generates an error message that reveals the path.
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 confidenceThe shtml.exe program in FrontPage Server Extensions for IIS 4.0 and 5.0 contains an information disclosure vulnerability. Remote attackers can determine the physical path of web root directories by requesting non-existent HTML, HTM, ASP, or SHTML files, which generates an error message revealing the full server filesystem path.
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 dataall versions= 4.0= 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 versionRun 'inetmgr' or check the Windows registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp' for the VersionString valueAffected if Version is 4.0 or 5.0 (IIS 4.0 or 5.0)
-
Confirm FrontPage Server Extensions presenceCheck for the presence of the 'shtml.exe' file in the FrontPage Server Extensions directory, typically found in '/_vti_bin/shtml.exe' or '\Program Files\Common Files\Microsoft Shared\web server extensions\'Affected if shtml.exe exists and is accessible via the web server
-
Check shtml.exe handler mappingIn IIS Manager, navigate to the website, open 'Handler Mappings', and look for a mapping pointing to shtml.exe or shtml.dllAffected if A handler mapping for .shtml or shtml.exe is enabled
-
Test for path disclosure vulnerabilitySend an HTTP GET request for a non-existent file such as '/nonexistent123.html', '/nonexistent123.htm', '/nonexistent123.asp', or '/nonexistent123.shtml' and examine the error responseAffected if The error response contains a full local filesystem path (e.g., 'c:\inetpub\wwwroot\...')
-
Verify custom error page configurationIn IIS Manager, go to the website properties, 'Custom Errors' tab, and check if detailed error messages are enabled for HTTP status codes 404 and 500Affected if Detailed error messages are returned instead of generic custom error pages
A system is affected if it runs IIS 4.0 or 5.0 with FrontPage Server Extensions where shtml.exe is present and returns full filesystem paths in error messages for non-existent web files.
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 dataDisable or remove the shtml.exe handler, or update FrontPage Server Extensions to a patched version. Implement custom error pages that suppress detailed path information in HTTP responses.
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0413 — 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-0413 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