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

> Remote attackers can execute arbitrary commands on Askey access points via shell metacharacters in network analysis tools.

- **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:** 11 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pm7g-wr2h-x45m

## What is CVE-2020-15357?

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

### Official description

Network Analysis functionality in Askey AP5100W_Dual_SIG_1.01.097 and all prior versions allows remote attackers to execute arbitrary commands via a shell metacharacter in the ping, traceroute, or route options.

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

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

It affects 1 product.


Products: Askey Ap5100w Firmware.

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

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

## Is CVE-2020-15357 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-26201](https://insights.sbomify.com/CVE-2020-26201/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-15023](https://insights.sbomify.com/CVE-2020-15023/): Weak cryptography in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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