CVE-2000-0236
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 · uneditedNetscape Enterprise Server with Directory Indexing enabled allows remote attackers to list server directories via web publishing tags such as ?wp-ver-info and ?wp-cs-dump.
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 confidenceNetscape Enterprise Server with Directory Indexing enabled allows remote attackers to list server directories via web publishing query parameters (?wp-ver-info and ?wp-cs-dump). This exposes directory contents without authentication.
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= 3.5.1= 3.6CVSS 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.
-
Confirm Netscape Enterprise Server is installedIdentify if Netscape Enterprise Server is running on the system. Check running processes, installed software, or look for netscape-ent processes or port 80/443 listeners with Netscape server signatures.Affected if Netscape Enterprise Server is not present on the system, this CVE does not apply.
-
Check installed server versionDetermine the exact version of Netscape Enterprise Server. Common methods include checking the server admin interface, examining server headers, or running: 'ns-httpd -v' or reviewing server configuration files.Affected if The installed version is exactly 3.0, 3.5.1, or 3.6. Other versions are not affected by this specific CVE.
-
Verify directory indexing is enabledCheck the Netscape Enterprise Server configuration (typically in magnus.conf or obj.conf) for directory indexing settings. Look for 'DirectoryIndex' directives or indexing-related configuration that allows automatic listing of directory contents.Affected if Directory indexing is enabled. When enabled, the server will list directory contents automatically when no index file is present.
-
Check for web publishing extensionsTest if the vulnerable web publishing parameters are accepted by attempting to access URLs with '?wp-ver-info=' or '?wp-cs-dump=' query strings on directory paths, or check server configuration for web publishing module files (wp* files in the modules directory).Affected if The server responds to ?wp-ver-info or ?wp-cs-dump query parameters, indicating web publishing extensions are installed and active.
The system is affected only if Netscape Enterprise Server version 3.0, 3.5.1, or 3.6 is running with both directory indexing enabled AND web publishing extensions present, allowing unauthenticated directory listing via the wp-ver-info or wp-cs-dump parameters.
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 directory indexing in Netscape Enterprise Server configuration or remove the vulnerable web publishing extensions.
- 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-0236 — 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-0236 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