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

> An attacker with SSH restricted shell access can achieve root privileges via shell metacharacters, allowing sensitive data access on Spirent appliances.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3cp9-mrrh-w8pj

## What is CVE-2020-11733?

CVE-2020-11733 is a medium-severity command injection vulnerability in n/a, published on 13 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on Spirent TestCenter and Avalanche appliance admin interface firmware. An attacker, who already has access to an SSH restricted shell, can achieve root access via shell metacharacters. The attacker can then, for example, read sensitive files such as appliance admin configuration source code. This affects Spirent TestCenter and Avalanche products which chassis version <= 5.08. The SSH restricted shell is available with default credentials.

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

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

It affects 2 products.


Products: Spirent Avalanche, Spirent Testcenter.

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

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

## Is CVE-2020-11733 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11733 is a medium-severity command injection vulnerability in n/a, published on 13 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11733 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-11733/ (Markdown: https://insights.sbomify.com/CVE-2020-11733/index.md)
```

## Sources

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

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