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

> Physical attackers can interrupt boot to execute arbitrary commands with root privileges on OKER G955V1 routers.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** 18 Jan 2023
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-m3p9-hq48-8qv8

## What is CVE-2020-22007?

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

### Official description

OS Command Injection vulnerability in OKER G955V1 v1.03.02.20161128, allows physical attackers to interrupt the boot sequence and execute arbitrary commands with root privileges.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Okerthai G955v1 Firmware.

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

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

## Is CVE-2020-22007 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-22007 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2020-22007 is a medium-severity command injection vulnerability in n/a, published on 18 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-22007 exists.

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-22007/ (Markdown: https://insights.sbomify.com/CVE-2020-22007/index.md)
```

## Sources

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

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