dbcve.org
Web ServerApplication · Novell

CVE-1999-1081

MEDIUM · 5.0 CVSS v2.0 Published 2002-01-15
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
Vulnerability in files.pl script in Novell WebServer Examples Toolkit 2 allows remote attackers to read arbitrary files.

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

Path traversal vulnerability in the files.pl Perl script of Novell WebServer Examples Toolkit 2 allows remote attackers to read arbitrary system files by manipulating file path parameters.

MitigationRemove or disable the vulnerable files.pl script and restrict access to the examples toolkit on any affected Novell WebServer installations.

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:= 2.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
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 if Novell Web Server 2.0 is installed
    Check for the presence of Novell Web Server 2.0 installation directories or check the web server version via server headers or administration interface
    Affected if Novell Web Server version 2.0 is running
  2. Locate the files.pl script in the Examples Toolkit
    Search for the files.pl Perl script in typical example toolkit directories such as /examples/, /scripts/examples/, or the WebServer Examples Toolkit 2 installation path
    Affected if The files.pl script exists in the web server's document tree
  3. Verify the script is accessible via HTTP
    Attempt to access the files.pl script remotely or check web server configuration for mappings to the examples directory containing files.pl
    Affected if The script is reachable through the web server (not restricted by .htaccess, IP filters, or authentication)
  4. Check for path traversal vulnerability
    Send a request to files.pl with manipulated path parameters such as ../../../../etc/passwd or similar directory traversal sequences to confirm the vulnerability exists
    Affected if The script returns content from files outside the intended document directory

A user is affected if they run Novell Web Server 2.0 with the Examples Toolkit's files.pl script accessible and the script permits directory traversal in its file path parameters.

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 files.pl script and restrict access to the examples toolkit on any affected Novell WebServer installations.

Fix this in Web Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-1999-1081 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-1081 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