CVE-2000-0071
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 allows a remote attacker to obtain the real pathname of the document root by requesting non-existent files with .ida or .idq extensions.
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 confidenceIIS 4.0 contains an information disclosure vulnerability where requesting non-existent files with .ida or .idq extensions causes the server to return an error message that reveals the full filesystem path of the document root, allowing attackers to map server directory structures.
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= 3.0= 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 versionCheck the IIS version by inspecting the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\INetStp or by checking the properties of the IIS Admin service, or by running 'iisinfo' from the command line if available.Affected if The installed version is 3.0, 4.0, or 5.0.
-
Verify .ida/.idq ISAPI extension mapping existsOpen IIS Manager, expand the web server node, right-click on 'Web Service Extensions' or check the 'Home Directory' > 'Configuration' > 'Mappings' tab to see if .ida and .idq extensions are mapped to an ISAPI DLL (such as idq.dll).Affected if The .ida and/or .idq extension mappings exist in IIS configuration.
-
Test for path disclosure vulnerabilityUsing a web browser or curl command, make an HTTP GET request to a non-existent file with the .ida extension, for example: http://targetserver/nonexistentfile.ida. Then repeat with .idq extension.Affected if The server responds with an error message that contains the full local filesystem path (such as C:\Inetpub\wwwroot\ or /inetpub/wwwroot/).
The environment is affected if IIS version 3.0, 4.0, or 5.0 is running with .ida or .idq ISAPI extensions enabled, and requesting non-existent .ida/.idq files reveals the server's filesystem paths.
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 dataApply the relevant Microsoft security patch for this vulnerability, or upgrade to a newer IIS version. If .ida/.idq extensions are not required for business functionality, disable these ISAPI extensions in IIS.
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0071 — 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-0071 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