CVE-2000-0063
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 · uneditedcgiproc CGI script in Nortel Contivity HTTP server allows remote attackers to read arbitrary files by specifying the filename in a parameter to the script.
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 confidenceThe cgiproc CGI script in Nortel Contivity HTTP server contains a path traversal vulnerability that allows remote attackers to read arbitrary files on the system by manipulating a filename parameter in the request. This is a classic directory traversal issue where the CGI script does not properly validate or sanitize user-supplied input specifying file paths.
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= 1.0CVSS 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.
-
Identify if Nortel Contivity HTTP server is installedCheck for Nortel Contivity installation directories or services on the system. Common paths may include installation directories under Program Files or system directories. Look for processes named 'contivity' or related services.Affected if The software is present on the system
-
Determine the installed version of Nortel ContivityLocate version information in the installation directory, registry entries, or by querying the service/process version. Compare the found version against the affected range: version 1.0.Affected if The installed version is exactly 1.0
-
Locate the cgiproc CGI scriptSearch for the cgiproc or cgiproc.exe file in the web server's CGI bin directory (commonly /cgi-bin/ or /cgi/). Check the Contivity web root for CGI scripts.Affected if The cgiproc script file exists on the system
-
Verify CGI script is accessible via HTTPAttempt to access the cgiproc script through the web server using a URL such as http://[host]/cgi-bin/cgiproc or similar path. Confirm the server responds to requests for this endpoint.Affected if The cgiproc script is accessible via HTTP and responds to requests
A user is affected if they have Nortel Contivity version 1.0 installed with the cgiproc CGI script present and accessible on their web server.
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 or remove the vulnerable cgiproc CGI script if not required, or apply vendor patches if available. If the script is required, implement strict input validation to prevent directory traversal sequences (../) and restrict access to allowed directories only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0063 — 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-0063 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