# CVE-2019-14417: Command injection in n/a

> A malicious user can execute arbitrary commands with root privileges in the VRP virtual machine via DNS functionality.

- **Severity:** High 7.2 (`CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:H/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pp8g-vhq4-49jm

## What is CVE-2019-14417?

CVE-2019-14417 is a high-severity command injection vulnerability in n/a, published on 29 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Veritas Resiliency Platform (VRP) before 3.4 HF1. An arbitrary command execution vulnerability allows a malicious VRP user to execute commands with root privilege within the VRP virtual machine, related to DNS functionality.

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

It affects 1 product.


Products: Veritas Resiliency Platform.

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

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

## Is CVE-2019-14417 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36168](https://insights.sbomify.com/CVE-2020-36168/): Path traversal in n/a (critical 9.3)
- [CVE-2019-14418](https://insights.sbomify.com/CVE-2019-14418/): Path traversal in n/a (critical 9.1)
- [CVE-2019-14416](https://insights.sbomify.com/CVE-2019-14416/): Command injection in n/a (high 7.2)
- [CVE-2019-14415](https://insights.sbomify.com/CVE-2019-14415/): Cross-site scripting in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14417 is a high-severity command injection vulnerability in n/a, published on 29 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-14417 in the wild and no public exploit code.

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

## Sources

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

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