# CVE-2009-4330: Other in n/a

> An unspecified local vulnerability in IBM DB2 Engine Utilities allows attackers with local access to potentially compromise the system.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7prh-r8q6-c94g

## What is CVE-2009-4330?

CVE-2009-4330 is a high-severity vulnerability in Ibm Db2, published on 16 Dec 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in db2licm in the Engine Utilities component in IBM DB2 9.5 before FP5 has unknown impact and local attack vectors.

## Which versions are affected by CVE-2009-4330?

It affects 1 product.


Products: Ibm Db2.

## How do I fix CVE-2009-4330?

No fix has been published for CVE-2009-4330 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-4330 being exploited?

There is no known exploitation of CVE-2009-4330 in the wild and no public exploit code.

## Other vulnerabilities in Ibm Db2

- [CVE-2012-1797](https://insights.sbomify.com/CVE-2012-1797/): IBM DB2 9.5 uses world-writable permissions for nodes.reg, which has unspecified impact and attack vectors. (critical 10.0)
- [CVE-2010-3731](https://insights.sbomify.com/CVE-2010-3731/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-3193](https://insights.sbomify.com/CVE-2010-3193/): Other in n/a (critical 10.0)
- [CVE-2009-4335](https://insights.sbomify.com/CVE-2009-4335/): Other in n/a (critical 10.0)
- [CVE-2009-3473](https://insights.sbomify.com/CVE-2009-3473/): Missing authorization in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4330 and fix it if it is affected.

What it is: CVE-2009-4330 is a high-severity vulnerability in Ibm Db2, published on 16 Dec 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-4330 in the wild and no public exploit code.

Affected product: Ibm Db2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2009-4330/ (Markdown: https://insights.sbomify.com/CVE-2009-4330/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2009-4330
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-4330
- OSV: https://osv.dev/vulnerability/CVE-2009-4330

---
From sbomify Insights: https://insights.sbomify.com/CVE-2009-4330/
Summaries are generated and may contain mistakes; the official description above is the record.