# CVE-2023-39222: Command injection in ACERA 1010

> Authenticated attackers can execute arbitrary OS commands on FURUNO wireless access points running in Standalone mode via crafted web requests.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2023
- **Updated:** 20 Sep 2024
- **Also known as:** GHSA-r3g8-4jx6-qh2v

## What is CVE-2023-39222?

CVE-2023-39222 is a high-severity command injection vulnerability in FURUNO SYSTEMS Co.,Ltd. ACERA 1010, published on 3 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OS command injection vulnerability in FURUNO SYSTEMS wireless LAN access point devices allows an authenticated user to execute an arbitrary OS command that is not intended to be executed from the web interface by sending a specially crafted request. Affected products and versions are as follows: ACERA 1320 firmware ver.01.26 and earlier, ACERA 1310 firmware ver.01.26 and earlier, ACERA 1210 firmware ver.02.36 and earlier, ACERA 1150i firmware ver.01.35 and earlier, ACERA 1150w firmware ver.01.35 and earlier, ACERA 1110 firmware ver.01.76 and earlier, ACERA 1020 firmware ver.01.86 and earlier, ACERA 1010 firmware ver.01.86 and earlier, ACERA 950 firmware ver.01.60 and earlier, ACERA 850F firmware ver.01.60 and earlier, ACERA 900 firmware ver.02.54 and earlier, ACERA 850M firmware ver.02.06 and earlier, ACERA 810 firmware ver.03.74 and earlier, and ACERA 800ST firmware ver.07.35 and earlier. They are affected when running in ST(Standalone) mode.

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

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

It affects 14 products.


Products: Furunosystems Acera 1010 Firmware, Furunosystems Acera 1020 Firmware, Furunosystems Acera 1110 Firmware, Furunosystems Acera 1150i Firmware, Furunosystems Acera 1150w Firmware, Furunosystems Acera 1210 Firmware, Furunosystems Acera 1310 Firmware, Furunosystems Acera 1320 Firmware, Furunosystems Acera 800st Firmware, Furunosystems Acera 810 Firmware, Furunosystems Acera 850f Firmware, Furunosystems Acera 850m Firmware, Furunosystems Acera 900 Firmware, Furunosystems Acera 950 Firmware.

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

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

## Is CVE-2023-39222 being exploited?

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

## Other vulnerabilities in FURUNO SYSTEMS Co.,Ltd. ACERA 1010

- [CVE-2023-41086](https://insights.sbomify.com/CVE-2023-41086/): Cross-site request forgery in ACERA 1010 (high 8.8)
- [CVE-2023-39429](https://insights.sbomify.com/CVE-2023-39429/): Cross-site scripting in ACERA 1010 (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39222 is a high-severity command injection vulnerability in FURUNO SYSTEMS Co.,Ltd. ACERA 1010, published on 3 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-39222 in the wild and no public exploit code.

Affected product: FURUNO SYSTEMS Co.,Ltd. ACERA 1010. 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-39222/ (Markdown: https://insights.sbomify.com/CVE-2023-39222/index.md)
```

## Sources

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

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