CVE-1999-0269
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 servers may list files through the PageServices query.
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 confidenceNetscape Enterprise Server contains a vulnerability where the PageServices query parameter can be manipulated to list files in server directories, leading to information disclosure. This allows attackers to enumerate file structures and potentially discover sensitive 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 dataall versionsCVSS 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 presentIdentify if Netscape Enterprise Server is running on the system by checking running processes, installed software, or listening on common web ports (typically ports 80, 443, or 8080). Look for 'netscape' or 'enterprise' in process names or service descriptions.Affected if Netscape Enterprise Server is found running on the system
-
Identify web server document rootLocate the web server's document root directory by examining server configuration files, typically found in the Netscape Enterprise Server configuration (often under 'https-<hostname>' or 'http-<hostname>' directories in the server root).Affected if Document root is identified and the server is confirmed as Netscape Enterprise Server
-
Test PageServices endpoint for directory listingSend an HTTP GET request to the server with a query parameter targeting the PageServices functionality. Example: Access a directory on the server with a crafted request such as 'GET /?PageServices=../../' or similar path traversal patterns that invoke directory listing.Affected if The server returns a listing of files or directories instead of a 403/404 error, indicating the vulnerability is present
-
Verify directory listing is enabledAttempt to access a known directory on the server without specifying a default file (like index.html). Check if the server returns a directory listing showing file names.Affected if Directory listing is returned showing file contents of the requested path
If Netscape Enterprise Server is running and the PageServices parameter allows directory traversal or listing files without authentication, the environment is affected by CVE-1999-0269.
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 listing functionality in Netscape Enterprise Server configuration, or migrate to a supported web server as Netscape Enterprise Server is obsolete.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0269 — 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-1999-0269 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