# CVE-2007-6049: Privilege escalation in n/a

> Privilege escalation vulnerability in IBM DB2 SSL action allows root-level code execution via dlopen, requiring high privileges to exploit.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m2r4-595q-cv76

## What is CVE-2007-6049?

CVE-2007-6049 is a high-severity vulnerability in Ibm Db2 Universal Database, published on 20 Nov 2007. 

### Official description

Unspecified vulnerability in the SSL LOAD GSKIT action in IBM DB2 UDB 9.1 before Fixpak 4 has unknown impact and attack vectors, involving a call to dlopen when the effective uid is root.

Weakness: CWE-264

## Which versions are affected by CVE-2007-6049?

It affects 1 product.


Products: Ibm Db2 Universal Database.

## How do I fix CVE-2007-6049?

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

## Is CVE-2007-6049 being exploited?

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

## Other vulnerabilities in Ibm Db2 Universal Database

- [CVE-2007-6045](https://insights.sbomify.com/CVE-2007-6045/): Unspecified vulnerability in (1) DB2WATCH and (2) DB2FREEZE in IBM DB2 UDB 9.1 before Fixpak 4 has unknown impact and attack vectors. (critical 10.0)
- [CVE-2007-6047](https://insights.sbomify.com/CVE-2007-6047/): Command injection in n/a (critical 10.0)
- [CVE-2007-6048](https://insights.sbomify.com/CVE-2007-6048/): Misconfiguration in n/a (critical 10.0)
- [CVE-2007-6051](https://insights.sbomify.com/CVE-2007-6051/): IBM DB2 UDB 9.1 before Fixpak 4 assigns incorrect privileges to the (1) DB2ADMNS and (2) DB2USERS alternative groups, which has unknown impact. (critical 10.0)
- [CVE-2005-4865](https://insights.sbomify.com/CVE-2005-4865/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6049 and fix it if it is affected.

What it is: CVE-2007-6049 is a high-severity vulnerability in Ibm Db2 Universal Database, published on 20 Nov 2007. 
Exploitation: There is no known exploitation of CVE-2007-6049 in the wild and no public exploit code.

Affected product: Ibm Db2 Universal Database. 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-2007-6049/ (Markdown: https://insights.sbomify.com/CVE-2007-6049/index.md)
```

## Sources

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

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