CVE-2001-1143
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 DB2 7.0 allows a remote attacker to cause a denial of service (crash) via a single byte to (1) db2ccs.exe on port 6790, or (2) db2jds.exe on port 6789.
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 DB2 7.0 contains a denial of service vulnerability where sending a single byte to either db2ccs.exe on port 6790 or db2jds.exe on port 6789 causes the service to crash. This is a remote, unauthenticated DoS affecting these specific DB2 components.
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= 7.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.
-
Confirm DB2 version is 7.0Use the DB2 command line processor (db2level) or check the installed version through the DB2 installation directory or Windows registry to determine the exact version installed.Affected if The installed version is exactly 7.0 (IBM DB2 Universal Database version 7.0)
-
Identify if db2ccs.exe or db2jds.exe processes are runningCheck running processes on the system for db2ccs.exe or db2jds.exe using task manager or command-line process listing tools.Affected if Either db2ccs.exe or db2jds.exe processes are currently running on the system
-
Verify if ports 6789 or 6790 are listeningUse netstat or similar network utility to check if the system is listening on TCP ports 6789 (db2jds) or 6790 (db2ccs).Affected if The system has TCP ports 6789 or 6790 open and listening for connections
-
Check for crash symptoms on affected portsSend a single byte of data to port 6789 or 6790 and observe if the corresponding service (db2jds or db2ccs) crashes or becomes unresponsive.Affected if Sending a single byte to either port causes the service to crash or stop responding
A system is affected if it runs IBM DB2 version 7.0 with db2ccs.exe or db2jds.exe processes listening on ports 6790 or 6789 respectively, and the services crash when sent a single byte of data.
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 DB2 to a patched version beyond 7.0, or if patching is not feasible, restrict network access to ports 6789 and 6790 via firewall rules to prevent unauthenticated remote attacks.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-1143 — 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-2001-1143 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