Menu

Star on GitHub · 3.2k

CVE-2001-1143

5.0 · MEDIUM

IBM 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.

Published Jul 11, 2001ibmEPSS 1.63%

Overview

CVE-2001-1143 is a medium-severity vulnerability affecting ibm db2_universal_database. It was published on July 11, 2001 and has a CVSS 2.0 base score of 5.0 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 5.0, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

IBM 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.

Remediation

Check the references section for vendor advisories and patches from ibm. Update db2_universal_database to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2001-1143?

CVE-2001-1143 is a medium-severity vulnerability affecting ibm db2_universal_database. It was published on July 11, 2001 and has a CVSS 2.0 base score of 5.0 (MEDIUM).

How severe is CVE-2001-1143?

This vulnerability has a CVSS 2.0 base score of 5.0, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2001-1143?

Check the references section for vendor advisories and patches from ibm. Update db2_universal_database to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2001-1143?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2001-1143 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2001

View all