# CVE-2024-9138: Privilege Escalation in Cellular Router, Secure Router, and Network Security Appliances

> Hard-coded credentials allow authenticated users to escalate privileges to root on Moxa routers and security appliances.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2025
- **Updated:** 3 Jan 2025
- **Also known as:** GHSA-wv93-f9g8-qg2r

## What is CVE-2024-9138?

CVE-2024-9138 is a high-severity vulnerability in Moxa EDF-G1002-BP Series, published on 3 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Moxa’s cellular routers, secure routers, and network security appliances are affected by a high-severity vulnerability, CVE-2024-9138. This vulnerability involves hard-coded credentials, enabling an authenticated user to escalate privileges and gain root-level access to the system, posing a significant security risk.

Weakness: CWE-656 (Reliance on Security Through Obscurity)

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


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

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

## Is CVE-2024-9138 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9138 is a high-severity vulnerability in Moxa EDF-G1002-BP Series, published on 3 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-9138 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-9138/ (Markdown: https://insights.sbomify.com/CVE-2024-9138/index.md)
```

## Sources

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

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