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

> An insecure file copy vulnerability in BMC Control-M Agent allows attackers to escalate privileges on the affected system.

- **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:** No
- **Published:** 30 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qc7r-vrf5-g6m3

## What is CVE-2019-19216?

CVE-2019-19216 is a high-severity vulnerability in n/a, published on 30 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BMC Control-M/Agent 7.0.00.000 has an Insecure File Copy.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Bmcsoftware Control-M\/Agent.

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

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

## Is CVE-2019-19216 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19215](https://insights.sbomify.com/CVE-2019-19215/): Memory corruption in n/a (high 8.8)
- [CVE-2019-19217](https://insights.sbomify.com/CVE-2019-19217/): Command injection in n/a (high 8.8)
- [CVE-2019-19220](https://insights.sbomify.com/CVE-2019-19220/): Command injection in n/a (high 8.8)
- [CVE-2019-19218](https://insights.sbomify.com/CVE-2019-19218/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2019-19219](https://insights.sbomify.com/CVE-2019-19219/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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