Web ServerApplication · Novell

CVE-1999-0175

MEDIUM · 5.0 CVSS v2.0 Published 1996-07-01
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
The convert.bas program in the Novell web server allows a remote attackers to read any file on the system that is internally accessible by the web server.

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

The convert.bas program in Novell Web Server contains a path traversal vulnerability allowing remote attackers to read arbitrary files accessible to the web server process. This is a classic file disclosure flaw where insufficient input validation on the convert.bas script enables directory traversal attacks.

MitigationRemove or disable the vulnerable convert.bas script from the web server. If the script is required, implement strict input validation and access controls to prevent directory traversal. Consider upgrading to a supported web server platform as Novell Web Server from this era is likely end-of-life.

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
Web ServerApplication
Affected:= 1.0

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
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/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 if Novell Web Server 1.0 is installed
    Check the installed software or running services for Novell Web Server version 1.0. On Windows, check Add/Remove Programs or the web server installation directory. Look for the presence of Novell web server binaries or documentation.
    Affected if Novell Web Server version 1.0 is found installed on the system
  2. Locate the convert.bas script
    Search the web server document root for the convert.bas file. Common paths may include /cgi-bin/ or the root web directory. Check for files named convert.bas in CGI or script directories.
    Affected if The convert.bas script exists in the web server's directory structure
  3. Verify the script is web-accessible
    Attempt to access http://your-server/cgi-bin/convert.bas or similar paths via HTTP to confirm the script is reachable over the web. Check web server configuration for CGI script mappings.
    Affected if The convert.bas script responds to HTTP requests and is publicly accessible
  4. Test for directory traversal vulnerability
    Send a crafted request to convert.bas with path traversal sequences such as ../../../../etc/passwd or ../../../../win.ini to attempt accessing files outside the web root. Observe if the server returns file contents.
    Affected if The script returns content from files outside the intended directory, confirming the vulnerability is exploitable
  5. Check for evidence of exploitation
    Review web server access logs for requests to convert.bas containing ../ sequences. Check for unusual file access patterns or unauthorized disclosure of sensitive system files.
    Affected if Logs show directory traversal attempts against convert.bas or unauthorized file reads have occurred

A system is affected if Novell Web Server 1.0 is running with the convert.bas script accessible via HTTP and the directory traversal vulnerability is present or has been exploited.

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

Remove or disable the vulnerable convert.bas script from the web server. If the script is required, implement strict input validation and access controls to prevent directory traversal. Consider upgrading to a supported web server platform as Novell Web Server from this era is likely end-of-life.

Fix this in Web Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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