# CVE-2019-16283: Code injection in HP Softpaq installer

> An attacker can execute arbitrary code via the HP Softpaq installer, posing a risk to users installing HP software.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 9 Jun 2023
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-5gxg-33gj-54pc

## What is CVE-2019-16283?

CVE-2019-16283 is a high-severity code injection vulnerability in HP Softpaq installer, published on 9 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential security vulnerability has been identified with a version of the HP Softpaq installer that can lead to arbitrary code execution.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Hp Softpaq Installer.

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

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

## Is CVE-2019-16283 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16283 is a high-severity code injection vulnerability in HP Softpaq installer, published on 9 Jun 2023. 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-16283 in the wild and no public exploit code.

Affected product: HP Softpaq installer. 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-16283/ (Markdown: https://insights.sbomify.com/CVE-2019-16283/index.md)
```

## Sources

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

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