# CVE-2019-12578: Privilege escalation in n/a

> A local attacker can escalate privileges to root by exploiting a setuid binary that allows arbitrary script execution via the --route-pre-down parameter.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 11 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rrp6-fm72-rh56

## What is CVE-2019-12578?

CVE-2019-12578 is a high-severity vulnerability in n/a, published on 11 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the London Trust Media Private Internet Access (PIA) VPN Client v82 for Linux could allow an authenticated, local attacker to run arbitrary code with elevated privileges. The openvpn_launcher.64 binary is setuid root. This binary executes /opt/pia/openvpn-64/openvpn, passing the parameters provided from the command line. Care was taken to programmatically disable potentially dangerous openvpn parameters; however, the --route-pre-down parameter can be used. This parameter accepts an arbitrary path to a script/program to be executed when OpenVPN exits. The --script-security parameter also needs to be passed to allow for this action to be taken, and --script-security is not currently in the disabled parameter list. A local unprivileged user can pass a malicious script/binary to the --route-pre-down option, which will be executed as root when openvpn is stopped.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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

It affects 1 product.


Products: Londontrustmedia Private Internet Access Vpn Client.

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

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

## Is CVE-2019-12578 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12574](https://insights.sbomify.com/CVE-2019-12574/): Privilege escalation in n/a (high 7.8)
- [CVE-2019-12575](https://insights.sbomify.com/CVE-2019-12575/): Privilege escalation in n/a (high 7.8)
- [CVE-2019-12576](https://insights.sbomify.com/CVE-2019-12576/): Privilege escalation in n/a (high 7.8)
- [CVE-2019-12577](https://insights.sbomify.com/CVE-2019-12577/): Privilege escalation in n/a (high 7.8)
- [CVE-2019-12579](https://insights.sbomify.com/CVE-2019-12579/): Command injection in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12578 is a high-severity vulnerability in n/a, published on 11 Jul 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-12578 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-12578/ (Markdown: https://insights.sbomify.com/CVE-2019-12578/index.md)
```

## Sources

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

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