Menu

Star on GitHub · 3.2k

CVE-2009-4150

4.6 · MEDIUM

dasauto in IBM DB2 8 before FP18, 9.1 before FP8, 9.5 before FP4, and 9.7 before FP1 permits execution by unprivileged user accounts, which has unspecified impact and local attack vectors.

Published Dec 2, 2009ibmCWE-264EPSS 0.44%

Overview

CVE-2009-4150 is a medium-severity vulnerability affecting ibm db2. It was published on December 2, 2009 and has a CVSS 2.0 base score of 4.6 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 4.6, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

dasauto in IBM DB2 8 before FP18, 9.1 before FP8, 9.5 before FP4, and 9.7 before FP1 permits execution by unprivileged user accounts, which has unspecified impact and local attack vectors.

Remediation

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

CVE-2009-4150 is a medium-severity vulnerability affecting ibm db2. It was published on December 2, 2009 and has a CVSS 2.0 base score of 4.6 (MEDIUM).

How severe is CVE-2009-4150?

This vulnerability has a CVSS 2.0 base score of 4.6, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2009-4150?

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

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

View all