# CVE-2024-11737: Denial of service in Modicon Controllers M241 / M251

> Unauthenticated attackers can cause denial of service and compromise data integrity via crafted Modbus packets on Schneider Modicon controllers.

- **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:** 11 Dec 2024
- **Updated:** 11 Dec 2024
- **Also known as:** GHSA-j45x-3v7g-qxh8

## What is CVE-2024-11737?

CVE-2024-11737 is a critical denial of service vulnerability in Schneider Electric Modicon Controllers M241 / M251, published on 11 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CWE-20: Improper Input Validation vulnerability exists that could lead to a denial of service and a loss of
confidentiality, integrity of the controller when an unauthenticated crafted Modbus packet is sent to the device.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2024-11737 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11737 is a critical denial of service vulnerability in Schneider Electric Modicon Controllers M241 / M251, published on 11 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-11737 in the wild and no public exploit code.

Affected product: Schneider Electric Modicon Controllers M241 / M251. 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-11737/ (Markdown: https://insights.sbomify.com/CVE-2024-11737/index.md)
```

## Sources

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

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