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

> Attackers can escalate privileges via PATH inheritance in OpenDoas when configured to allow arbitrary command execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jan 2021
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2019-25016, GHSA-59xc-99wg-3hgf

## What is CVE-2019-25016?

CVE-2019-25016 is a high-severity vulnerability in n/a, published on 28 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In OpenDoas from 6.6 to 6.8 the users PATH variable was incorrectly inherited by authenticated executions if the authenticating rule allowed the user to execute any command. Rules that only allowed to authenticated user to execute specific commands were not affected by this issue.

Weakness: CWE-909 (Missing Initialization of Resource), CWE-459 (Incomplete Cleanup)

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

It affects 1 product.


Products: Opendoas Project Opendoas.

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

Apply the vendor's patch.

## Is CVE-2019-25016 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-28339](https://insights.sbomify.com/CVE-2023-28339/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25016 is a high-severity vulnerability in n/a, published on 28 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-25016 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-25016/ (Markdown: https://insights.sbomify.com/CVE-2019-25016/index.md)
```

## Sources

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

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