# CVE-2024-9140: Command injection in EDF-G1002-BP Series

> Attackers can execute arbitrary code on Moxa routers and appliances via OS command injection, requiring immediate patching.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2025
- **Updated:** 3 Jan 2025
- **Also known as:** GHSA-mqhc-c63f-9fc8

## What is CVE-2024-9140?

CVE-2024-9140 is a critical command injection vulnerability in Moxa EDF-G1002-BP Series, published on 3 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Moxa’s cellular routers, secure routers, and network security appliances are affected by a critical vulnerability, CVE-2024-9140. This vulnerability allows OS command injection due to improperly restricted commands, potentially enabling attackers to execute arbitrary code. This poses a significant risk to the system’s security and functionality.

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

## Which versions are affected by CVE-2024-9140?


## How do I fix CVE-2024-9140?

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

## Is CVE-2024-9140 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-9140 and fix it if it is affected.

What it is: CVE-2024-9140 is a critical command injection vulnerability in Moxa EDF-G1002-BP Series, published on 3 Jan 2025. 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-2024-9140 in the wild and no public exploit code.

Affected product: Moxa EDF-G1002-BP Series. 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-2024-9140/ (Markdown: https://insights.sbomify.com/CVE-2024-9140/index.md)
```

## Sources

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

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