CVE-2000-0677
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 · uneditedBuffer overflow in IBM Net.Data db2www CGI program allows remote attackers to execute arbitrary commands via a long PATH_INFO environmental variable.
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 confidenceBuffer overflow vulnerability in IBM Net.Data db2www CGI program allows remote attackers to execute arbitrary commands via an overly long PATH_INFO environmental variable, enabling complete system compromise.
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 dataall versionsCVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check if IBM Net.Data is installed on the systemSearch for Net.Data installation directories (common paths: /opt/ibm/net.data, /usr/lpp/net.data, C:\Program Files\IBM\Net.Data) or check for net.data related files using: find / -name '*net.data*' 2>/dev/null (Unix) or dir /s /b C:\*net.data* 2>nul (Windows)Affected if IBM Net.Data installation directories or files are found on the system
-
Locate the db2www CGI programSearch for the db2www executable in typical CGI directories (cgi-bin, cgi-win, /httpd/cgi-bin) or within Net.Data installation paths. Use: find / -name 'db2www*' 2>/dev/null (Unix) or dir /s /b C:\db2www* 2>nul (Windows)Affected if The db2www CGI program file exists on the system
-
Verify if the db2www CGI is web-accessibleCheck web server configuration files (httpd.conf, .htaccess) for CGI script aliases pointing to db2www, or attempt a simple HTTP request to known CGI paths (e.g., /cgi-bin/db2www) if the web server is accessibleAffected if The db2www CGI is configured as a handler in the web server and reachable via HTTP
-
Confirm the web server has CGI execution enabledInspect the web server configuration for 'ScriptAlias' directives, 'Options +ExecCGI', or 'AddHandler cgi-script' entries that enable CGI processing for the directory containing db2wwwAffected if CGI execution is enabled for the directory where db2www is located
The environment is affected if IBM Net.Data with the db2www CGI program is installed and web-accessible, since all versions contain the buffer overflow vulnerability in the PATH_INFO handling.
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.
dbcve · scopedRemove or disable the vulnerable db2www CGI program if IBM Net.Data is not required, or apply vendor patches if available.
- If the db2www CGI program is not required, remove or delete it from the web server to eliminate the vulnerability.
- If the CGI is required, restrict access to it via web server authentication (e.g., IP allowlist, basic auth, or VPN) to prevent unauthored remote attackers from reaching it.
- Configure the web server to limit or reject excessively long PATH_INFO requests as a defensive measure.
- Audit the web server for any other legacy CGI scripts that may have similar vulnerabilities.
- If IBM Net.Data is still in production use, evaluate migrating to a supported IBM data access solution.
- Consider network segmentation to isolate systems running legacy CGI applications.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing4.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 $4,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0677 — 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-0677 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