# CVE-2021-37384: Command injection in n/a

> Remote unauthenticated attackers can execute arbitrary commands on Furukawa ONU devices via the web interface.

- **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:** 17 Jul 2023
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7m3j-v6wq-hr22

## What is CVE-2021-37384?

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

### Official description

RCE (Remote Code Execution) vulnerability was found in some Furukawa ONU models, this vulnerability allows remote unauthenticated users to send arbitrary commands to the device via web interface.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2021-37384?

It affects 4 products.


Products: Furukawa 423-41w\/Ac Firmware, Furukawa Ld420-10r Firmware, Furukawa Ld421-21w Firmware, Furukawa Ld421-21wv Firmware.

## How do I fix CVE-2021-37384?

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

## Is CVE-2021-37384 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-37386](https://insights.sbomify.com/CVE-2021-37386/): Cross-site scripting in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-37384 and fix it if it is affected.

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

## Sources

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

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