# CVE-2018-20122: Command injection in n/a

> Unauthenticated attackers can execute arbitrary commands with root privileges via a vulnerable CGI binary in the web interface.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 21 Feb 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-93p5-p6gm-m2rg

## What is CVE-2018-20122?

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

### Official description

The web interface on FASTGate Fastweb devices with firmware through 0.00.47_FW_200_Askey 2017-05-17 (software through 1.0.1b) exposed a CGI binary that is vulnerable to a command injection vulnerability that can be exploited to achieve remote code execution with root privileges. No authentication is required in order to trigger the vulnerability.

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

## Which versions are affected by CVE-2018-20122?

It affects 1 product.


Products: Fastweb Fastgate Firmware.

## How do I fix CVE-2018-20122?

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

## Is CVE-2018-20122 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-6023](https://insights.sbomify.com/CVE-2018-6023/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-18661](https://insights.sbomify.com/CVE-2019-18661/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20122 and fix it if it is affected.

What it is: CVE-2018-20122 is a critical command injection vulnerability in n/a, published on 21 Feb 2019. 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-2018-20122 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-2018-20122/ (Markdown: https://insights.sbomify.com/CVE-2018-20122/index.md)
```

## Sources

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

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