HTTP ServerWeb server / proxy · Ibm
CVE-2000-1168
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 · uneditedIBM HTTP Server 1.3.6 (based on Apache) allows remote attackers to cause a denial of service and possibly execute arbitrary commands via a long GET request.
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 · moderate confidenceIBM HTTP Server 1.3.6, built on Apache 1.3.x, contains a vulnerability where malformed or excessively long GET requests can trigger a buffer overflow, enabling remote attackers to cause denial of service and potentially execute arbitrary commands.
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
HTTP ServerWeb server / proxy
= 1.3.6.3CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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 IBM HTTP Server installationCheck for IBM HTTP Server binary or service: look for 'ibmhttp' process, check /usr/local/ibmHTTPServer or similar installation directories, or query the web server directly via HTTP headersAffected if IBM HTTP Server is installed and running
-
Determine installed versionQuery the server version via HTTP headers (curl -I <server>) or check the binary version: apachectl -v, or look at version strings in httpd binaryAffected if Version is exactly 1.3.6.3 (this specific version is vulnerable)
-
Verify service is network accessibleCheck if HTTP/HTTPS ports are open and listening: netstat -tlnp | grep -E ':(80|443|8000|8080)'Affected if The IBM HTTP Server is exposed to network or untrusted users
-
Confirm Apache 1.3.x baseInspect server response headers or run: strings <httpd_binary> | grep 'Apache/' to confirm base version is 1.3.xAffected if Built on Apache 1.3.x codebase (the vulnerability exists in this base)
-
Check for abnormal request handling logsReview access and error logs for unusually long GET requests, malformed requests, or crash indicators: grep -E 'GET.*\.{200,}' access_logAffected if Logs show evidence of malformed or excessively long requests hitting the server
You are affected only if IBM HTTP Server version 1.3.6.3 is installed and accessible over the network, as this specific version contains the buffer overflow flaw in handling long GET requests.
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 dataUpgrade IBM HTTP Server to a patched version or migrate to a supported Apache release. If immediate patching is not feasible, consider placing a WAF or reverse proxy in front to filter abnormally long HTTP requests.
Fix this in HTTP Server
Scoped from the published advisory
- 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-1168 — 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-1168 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