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

> Remote attackers can execute arbitrary commands on Mercury Router devices via the PPTP server service.

- **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:** 14 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j22p-f8jx-q4g5

## What is CVE-2020-22724?

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

### Official description

A remote command execution vulnerability exists in add_server_service of PPTP_SERVER in Mercury Router MER1200 v1.0.1 and Mercury Router MER1200G v1.0.1.

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

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

It affects 2 products.


Products: Mercury Mer1200 Firmware, Mercury Mer1200g Firmware.

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

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

## Is CVE-2020-22724 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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