# CVE-2019-4473: Code injection in Java

> Local attackers can exploit insecure RPATHs in IBM Java SDK binaries on AIX to execute arbitrary code and escalate privileges.

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

## What is CVE-2019-4473?

CVE-2019-4473 is a high-severity code injection vulnerability in IBM Java, published on 5 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple binaries in IBM SDK, Java Technology Edition 7, 7R, and 8 on the AIX platform use insecure absolute RPATHs, which may facilitate code injection and privilege elevation by local users. IBM X-Force ID: 163984.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Ibm Java.

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

Apply the vendor's patch.

## Is CVE-2019-4473 being exploited?

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

## Other vulnerabilities in IBM Java

- [CVE-2013-0485](https://insights.sbomify.com/CVE-2013-0485/): Other in n/a (critical 10.0)
- [CVE-2015-0192](https://insights.sbomify.com/CVE-2015-0192/): Privilege escalation in n/a (critical 9.8)
- [CVE-2013-5456](https://insights.sbomify.com/CVE-2013-5456/): Deserialization in n/a (critical 9.3)
- [CVE-2013-5457](https://insights.sbomify.com/CVE-2013-5457/): Code injection in n/a (critical 9.3)
- [CVE-2013-5458](https://insights.sbomify.com/CVE-2013-5458/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-4473 is a high-severity code injection vulnerability in IBM Java, published on 5 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-4473 in the wild and no public exploit code.

Affected product: IBM Java. 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-4473/ (Markdown: https://insights.sbomify.com/CVE-2019-4473/index.md)
```

## Sources

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

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