CVE-2000-0064
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 cause a denial of service via a malformed URL that includes shell metacharacters.
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 fails to properly sanitize shell metacharacters in malformed URLs, allowing remote attackers to crash the HTTP service via specially crafted requests containing characters like |, ;, or &.
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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 is installedCheck system for Nortel Contivity software installation, typically in Program Files or application directories, or check running services for Contivity processesAffected if Nortel Contivity software is present on the system
-
Confirm Contivity versionLocate the Contivity installation directory and check version information in about files, registry, or the application executable propertiesAffected if Version is 1.0 (the only affected version listed)
-
Check if HTTP server component is runningLook for Contivity HTTP server process or service running, typically on port 80 or 443, or check netstat for associated portsAffected if Contivity HTTP server is active and listening
-
Locate cgiproc CGI scriptSearch web document directories (htdocs, cgi-bin, cgi) for the cgiproc script fileAffected if cgiproc script exists in the web-accessible CGI directory
-
Verify script is accessible via HTTPAttempt to access the cgiproc script through the Contivity HTTP server using a web browser or curl (e.g., GET /cgi-bin/cgiproc)Affected if Script responds to HTTP requests (indicating CGI is enabled and script is accessible)
User is affected if running Nortel Contivity version 1.0 with the cgiproc CGI script accessible through the Contivity HTTP server, as the vulnerability allows remote denial of service via shell metacharacters in URLs
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 dataApply the vendor patch from Nortel for the Contivity product, or if unsupported, remove or disable the vulnerable cgiproc script and consider deploying a web application firewall to filter malicious requests.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0064 — 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-0064 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