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

> A local attacker with callrec account access can replace a root-owned binary to escalate privileges to root in ZOOM Call Recording.

- **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:** 14 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mh2m-wxr3-8fr6

## What is CVE-2019-18822?

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

### Official description

A privilege escalation vulnerability in ZOOM Call Recording 6.3.1 allows its user account (i.e., the account under which the program runs - by default, the callrec account) to elevate privileges to root by abusing the callrec-rs@.service. The callrec-rs@.service starts the /opt/callrec/bin/rs binary with root privileges, and this binary is owned by callrec. It can be replaced by a Trojan horse.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Eleveo Call Recording.

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

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

## Is CVE-2019-18822 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19810](https://insights.sbomify.com/CVE-2019-19810/): Deserialization in n/a (critical 10.0)
- [CVE-2019-18223](https://insights.sbomify.com/CVE-2019-18223/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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