# CVE-2022-48616: Command injection in AR6000

> Attackers can execute arbitrary commands on Huawei AR6000 routers to gain higher privileges.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:A/AC:H/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:** 12 Dec 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-p7xv-5v8m-5xcw

## What is CVE-2022-48616?

CVE-2022-48616 is a medium-severity command injection vulnerability in Huawei AR6000, published on 12 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Huawei data communication product has a command injection vulnerability. Successful exploitation of this vulnerability may allow attackers to gain higher privileges.

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

## Which versions are affected by CVE-2022-48616?

It affects 1 product.


Products: Huawei Ar617vw Firmware.

## How do I fix CVE-2022-48616?

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

## Is CVE-2022-48616 being exploited?

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

## Other vulnerabilities in Huawei AR6000

- [CVE-2022-48615](https://insights.sbomify.com/CVE-2022-48615/): Information disclosure in AR6000 (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48616 and fix it if it is affected.

What it is: CVE-2022-48616 is a medium-severity command injection vulnerability in Huawei AR6000, published on 12 Dec 2023. 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-2022-48616 in the wild and no public exploit code.

Affected product: Huawei AR6000. 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-2022-48616/ (Markdown: https://insights.sbomify.com/CVE-2022-48616/index.md)
```

## Sources

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

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