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

> Attackers can execute arbitrary commands as root and retrieve admin credentials on Askey Fiber Routers, leading to full device compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qcmf-8hrw-fxh3

## What is CVE-2020-28695?

CVE-2020-28695 is a high-severity command injection vulnerability in n/a, published on 26 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Askey Fiber Router RTF3505VW-N1 BR_SV_g000_R3505VWN1001_s32_7 devices allow Remote Code Execution and retrieval of admin credentials to log into the Dashboard or login via SSH, leading to code execution as root.

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

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

It affects 1 product.


Products: Askey Rtf3505vw-N1 Br Sv G000 R3505vwn1001 S32 7 Firmware.

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

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

## Is CVE-2020-28695 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28695 is a high-severity command injection vulnerability in n/a, published on 26 Mar 2021. 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-28695 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-28695/ (Markdown: https://insights.sbomify.com/CVE-2020-28695/index.md)
```

## Sources

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

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