CVE-2000-0126
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 · uneditedSample Internet Data Query (IDQ) scripts in IIS 3 and 4 allow remote attackers to read files via a .. (dot dot) attack.
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 3 and 4 shipped with sample Internet Data Query (IDQ) scripts that contain a path traversal vulnerability. Attackers can use '../' sequences in specially crafted requests to the IDQ scripts to access files outside the web root, potentially reading sensitive system files.
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.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 installed Microsoft IIS version by viewing the server properties in the IIS Manager snap-in or checking the registry key HKLM\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\MajorVersionAffected if The installed version is 3.0 or 4.0
-
Verify IDQ/IDA ISAPI extension is mappedIn IIS Manager, open the Web site properties, go to Home Directory tab, click Configuration, and check the Application Mappings list for .ida and .idq extensions mapped to idq.dllAffected if Mappings for .ida or .idq extensions to idq.dll exist and are enabled
-
Check for presence of sample IDQ filesLocate the IIS scripts directory (typically \scripts or \IISScripts) and search for files with .ida, .idq, or idq.dll extensionsAffected if Sample IDQ files (idq.dll, .ida, .idq files) exist in the scripts directory
-
Test IDQ endpoint accessibilitySend a crafted HTTP request to the server targeting an IDQ script path (such as /scripts/idq.dll or any .ida/.idq mapped file) using the '../' sequence to traverse outside the web rootAffected if The server processes IDQ requests and the path traversal sequence allows access to files outside the web root directory
A system is affected if it runs IIS 3.0 or 4.0 with IDQ/IDA ISAPI extension mappings enabled and sample IDQ scripts are present, allowing unauthenticated path traversal via specially crafted requests.
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 dataRemove all sample IDQ scripts (idq.dll and related .ida/.idq files) from the IIS scripts directory. Apply Microsoft security patches for this vulnerability. If IDQ/Indexing Service is not required, disable or remove the ISAPI extension entirely.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0126 — 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-0126 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