Enterprise ServerApplication · Netscape

CVE-1999-0758

MEDIUM · 5.0 CVSS v2.0 Published 2001-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Netscape Enterprise 3.5.1 and FastTrack 3.01 servers allow a remote attacker to view source code to scripts by appending a %20 to the script's URL.

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 confidence

Netscape Enterprise 3.5.1 and FastTrack 3.01 servers contain an information disclosure vulnerability where appending '%20' (URL-encoded space) to script URLs causes the server to return the unprocessed source code instead of executing the script. This allows remote attackers to view sensitive script contents including potential credentials, business logic, and database queries.

MitigationUpgrade to a supported Netscape server version or migrate to a modern web server platform. If the affected servers must remain in operation, isolate them behind a firewall and disable any scripts that may expose sensitive information.

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
Enterprise ServerApplication
Affected:= 3.5.1
Fasttrack ServerApplication
Affected:= 3.01

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the web server product and version
    Check the server banners, HTTP headers, or consult server documentation to determine if the web server is Netscape Enterprise Server or Netscape Fasttrack Server. Look for version strings in server responses or configuration files.
    Affected if The server is Netscape Enterprise Server version 3.5.1 or Netscape Fasttrack Server version 3.01 exactly
  2. Verify scripts are enabled and accessible
    Check the server configuration for enabled script handlers (CGI, NSAPI, or other server-side script execution modes). Confirm that script directories are accessible via HTTP.
    Affected if Server-side scripts are enabled and accessible over the network
  3. Test for source disclosure with URL-encoded space
    Make an HTTP GET request to a known script URL (such as a CGI script or server-side include) and append '%20' to the end of the URL path. For example: GET /scripts/example.cgi%20 HTTP/1.1
    Affected if The server returns the raw source code of the script instead of executing it or returning a 404 error

You are affected if you are running Netscape Enterprise Server 3.5.1 or Netscape Fasttrack Server 3.01 with scripts enabled and the server returns unprocessed script source code when '%20' is appended to script URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a supported Netscape server version or migrate to a modern web server platform. If the affected servers must remain in operation, isolate them behind a firewall and disable any scripts that may expose sensitive information.

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-1999-0758 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-1999-0758 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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