# CVE-2024-9137: Moxa Service Missing Authentication for Critical Function

> Attackers can execute commands and modify configurations on Moxa industrial devices due to missing authentication checks in the Moxa service.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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:** 14 Oct 2024
- **Updated:** 19 Sep 2025
- **Also known as:** GHSA-c5hh-282x-jrgh

## What is CVE-2024-9137?

CVE-2024-9137 is a high-severity missing authorization vulnerability in Moxa EDF-G1002-BP Series, published on 14 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The affected product lacks an authentication check when sending commands to the server via the Moxa service. This vulnerability allows an attacker to execute specified commands, potentially leading to unauthorized downloads or uploads of configuration files and system compromise.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2024-9137 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9137 is a high-severity missing authorization vulnerability in Moxa EDF-G1002-BP Series, published on 14 Oct 2024. 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-9137 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-9137/ (Markdown: https://insights.sbomify.com/CVE-2024-9137/index.md)
```

## Sources

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

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