# CVE-2023-30400: Command injection in n/a

> Attackers can execute arbitrary commands on Anyka AK3918EV300 MCUs by sending a crafted Wi-Fi SSID or password.

- **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:** 7 Jun 2023
- **Updated:** 7 Jan 2025
- **Also known as:** GHSA-76pq-9vqf-2pjv

## What is CVE-2023-30400?

CVE-2023-30400 is a critical command injection vulnerability in n/a, published on 7 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Anyka Microelectronics AK3918EV300 MCU v18. A command injection vulnerability in the network configuration script within the MCU's operating system allows attackers to perform arbitrary command execution via a crafted wifi SSID or password.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2023-30400?

It affects 1 product.


Products: Anyka Ak3918ev300 Firmware.

## How do I fix CVE-2023-30400?

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

## Is CVE-2023-30400 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30400 and fix it if it is affected.

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

## Sources

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

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