# CVE-2019-4447: Privilege escalation in DB2 High Performance Unload load for LUW

> A low-privileged user can gain root access by manipulating the PATH variable to execute arbitrary commands via a setuid binary.

- **Severity:** High 8.4 (`CVSS:3.0/I:H/AC:L/A:H/PR:N/UI:N/S:U/AV:L/C:H/E:U/RC:C/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-jrvj-hjx2-hc4m

## What is CVE-2019-4447?

CVE-2019-4447 is a high-severity vulnerability in IBM DB2 High Performance Unload load for LUW, published on 26 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM DB2 High Performance Unload load for LUW 6.1, 6.1.0.1, 6.1.0.1 IF1, 6.1.0.2, 6.1.0.2 IF1, and 6.1.0.1 IF2 db2hpum_debug is a setuid root binary which trusts the PATH environment variable. A low privileged user can execute arbitrary commands as root by altering the PATH variable to point to a user controlled location. When a crash is induced the trojan gdb command is executed. IBM X-Force ID: 163488.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2019-4447?

It affects 1 product.


Products: Ibm Db2 High Performance Unload Load.

## How do I fix CVE-2019-4447?

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

## Is CVE-2019-4447 being exploited?

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

## Other vulnerabilities in IBM DB2 High Performance Unload load for LUW

- [CVE-2019-4523](https://insights.sbomify.com/CVE-2019-4523/): Memory corruption in DB2 High Performance Unload load for LUW (high 8.4)
- [CVE-2019-4448](https://insights.sbomify.com/CVE-2019-4448/): Privilege escalation in DB2 High Performance Unload load for LUW (high 8.4)
- [CVE-2019-4606](https://insights.sbomify.com/CVE-2019-4606/): Other in DB2 High Performance Unload load for LUW (high 7.4)
- [CVE-2025-33126](https://insights.sbomify.com/CVE-2025-33126/): Fixes to common vulnerabilities found in IBM Db2 High Performance Unload (medium 6.5)
- [CVE-2025-33131](https://insights.sbomify.com/CVE-2025-33131/): Fixes to common vulnerabilities found in IBM Db2 High Performance Unload (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-4447 and fix it if it is affected.

What it is: CVE-2019-4447 is a high-severity vulnerability in IBM DB2 High Performance Unload load for LUW, published on 26 Aug 2019. 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-2019-4447 in the wild and no public exploit code.

Affected product: IBM DB2 High Performance Unload load for LUW. 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-2019-4447/ (Markdown: https://insights.sbomify.com/CVE-2019-4447/index.md)
```

## Sources

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

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