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

> Attackers can execute arbitrary commands and escalate privileges via DLL hijacking in Goverlan Reach components due to untrusted search paths.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-85h5-jgxc-3hpj

## What is CVE-2019-20456?

CVE-2019-20456 is a high-severity command injection vulnerability in n/a, published on 16 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Goverlan Reach Console before 9.50, Goverlan Reach Server before 3.50, and Goverlan Client Agent before 9.20.50 have an Untrusted Search Path that leads to Command Injection and Local Privilege Escalation via DLL hijacking.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 3 products.


Products: Goverlan Client Agent, Goverlan Reach Console, Goverlan Reach Server.

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

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

## Is CVE-2019-20456 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31215](https://insights.sbomify.com/CVE-2022-31215/): Security feature bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20456 is a high-severity command injection vulnerability in n/a, published on 16 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-20456 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-20456/ (Markdown: https://insights.sbomify.com/CVE-2019-20456/index.md)
```

## Sources

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

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