Menu

Star on GitHub · 3.2k

CVE-2009-2667

10.0 · HIGH

Unspecified vulnerability in IBM Tivoli Key Lifecycle Manager (TKLM) 1.0 has unknown impact and attack vectors, related to a "password security vulnerability."

Published Aug 5, 2009ibmEPSS 1.45%

Overview

CVE-2009-2667 is a high-severity vulnerability affecting ibm tklm. It was published on August 5, 2009 and has a CVSS 2.0 base score of 10.0 (HIGH).

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

Technical description

Unspecified vulnerability in IBM Tivoli Key Lifecycle Manager (TKLM) 1.0 has unknown impact and attack vectors, related to a "password security vulnerability."

Remediation

Check the references section for vendor advisories and patches from ibm. Update tklm 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-2009-2667?

CVE-2009-2667 is a high-severity vulnerability affecting ibm tklm. It was published on August 5, 2009 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2009-2667?

This vulnerability has a CVSS 2.0 base score of 10.0, 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-2009-2667?

Check the references section for vendor advisories and patches from ibm. Update tklm 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-2009-2667?

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

View all