# CVE-2019-4606: Other in DB2 High Performance Unload load for LUW

> A local attacker can execute arbitrary code on the system via an untrusted search path vulnerability in IBM DB2 High Performance Unload.

- **Severity:** High 7.4 (`CVSS:3.0/AC:H/PR:N/A:H/S:U/UI:N/I:H/AV:L/C:H/RC:C/E:U/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:** 12 Dec 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g2fc-4mpm-58fg

## What is CVE-2019-4606?

CVE-2019-4606 is a high-severity vulnerability in IBM DB2 High Performance Unload load for LUW, published on 12 Dec 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 and 6.5 could allow a local attacker to execute arbitrary code on the system, caused by an untrusted search path vulnerability. By using a executable file, an attacker could exploit this vulnerability to execute arbitrary code on the system. IBM X-Force ID: 168298.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Ibm Db2 High Performance Unload Load.

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

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

## Is CVE-2019-4606 being exploited?

There is no known exploitation of CVE-2019-4606 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-4447](https://insights.sbomify.com/CVE-2019-4447/): Privilege escalation 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-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-4606 and fix it if it is affected.

What it is: CVE-2019-4606 is a high-severity vulnerability in IBM DB2 High Performance Unload load for LUW, published on 12 Dec 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-4606 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-4606/ (Markdown: https://insights.sbomify.com/CVE-2019-4606/index.md)
```

## Sources

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

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