# CVE-2024-9404: Denial-of-Service Vulnerability

> Attackers can cause denial of service on Moxa industrial switches via the moxa_cmd service due to insufficient input validation.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/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:** 4 Dec 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-2gj6-9934-w9r6

## What is CVE-2024-9404?

CVE-2024-9404 is a medium-severity denial of service vulnerability in Moxa EDS-405A Series, published on 4 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability could lead to denial-of-service or service crashes. Exploitation of the moxa_cmd service, because of insufficient input validation, allows attackers to disrupt operations. If exposed to public networks, the vulnerability poses a significant remote threat, potentially allowing attackers to shut down affected systems.

Weakness: CWE-1287 (Improper Validation of Specified Type of Input)

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


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

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

## Is CVE-2024-9404 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9404 is a medium-severity denial of service vulnerability in Moxa EDS-405A Series, published on 4 Dec 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-9404 in the wild and no public exploit code.

Affected product: Moxa EDS-405A 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-9404/ (Markdown: https://insights.sbomify.com/CVE-2024-9404/index.md)
```

## Sources

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

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