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

> Attackers can execute arbitrary code by injecting payloads into election event aliases due to unsafe command execution in Scytl sVote.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2021
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r8r8-mhhg-vjch

## What is CVE-2019-25022?

CVE-2019-25022 is a critical command injection vulnerability in n/a, published on 27 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Scytl sVote 2.1. An attacker can inject code that gets executed by creating an election-event and injecting a payload over an event alias, because the application calls Runtime.getRuntime().exec() without validation.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Scytl Secure Vote.

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

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

## Is CVE-2019-25022 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-25020](https://insights.sbomify.com/CVE-2019-25020/): Missing authorization in n/a (high 7.5)
- [CVE-2019-25021](https://insights.sbomify.com/CVE-2019-25021/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2019-25023](https://insights.sbomify.com/CVE-2019-25023/): Other in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25022 is a critical command injection vulnerability in n/a, published on 27 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-25022 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-25022/ (Markdown: https://insights.sbomify.com/CVE-2019-25022/index.md)
```

## Sources

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

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