Menu

Star on GitHub · 3.2k

CVE-2001-0051

7.5 · HIGH

IBM DB2 Universal Database version 6.1 creates an account with a default user name and password, which allows remote attackers to gain access to the database.

Published Feb 16, 2001ibmEPSS 2.79%

Overview

CVE-2001-0051 is a high-severity vulnerability affecting ibm db2_universal_database. It was published on February 16, 2001 and has a CVSS 2.0 base score of 7.5 (HIGH).

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

Technical description

IBM DB2 Universal Database version 6.1 creates an account with a default user name and password, which allows remote attackers to gain access to the database.

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-0051?

CVE-2001-0051 is a high-severity vulnerability affecting ibm db2_universal_database. It was published on February 16, 2001 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2001-0051?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. 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-0051?

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-0051?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2001-0051 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 HIGH CVEs from 2001

View all