# CVE-2020-25094: Command injection in n/a

> Attackers can inject commands via WebSocket to execute arbitrary code with LocalSystem privileges on remote agents.

- **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:** 17 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r929-7jrv-6rh2

## What is CVE-2020-25094?

CVE-2020-25094 is a critical command injection vulnerability in n/a, published on 17 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LogRhythm Platform Manager 7.4.9 allows Command Injection. To exploit this, an attacker can inject arbitrary program names and arguments into a WebSocket. These are forwarded to any remote server with a LogRhythm Smart Response agent installed. By default, the commands are run with LocalSystem privileges.

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

## Which versions are affected by CVE-2020-25094?

It affects 1 product.


Products: Logrhythm Platform Manager.

## How do I fix CVE-2020-25094?

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

## Is CVE-2020-25094 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-25095](https://insights.sbomify.com/CVE-2020-25095/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-25096](https://insights.sbomify.com/CVE-2020-25096/): Missing authorization in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25094 and fix it if it is affected.

What it is: CVE-2020-25094 is a critical command injection vulnerability in n/a, published on 17 Dec 2020. 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-2020-25094 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-2020-25094/ (Markdown: https://insights.sbomify.com/CVE-2020-25094/index.md)
```

## Sources

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

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