# CVE-2019-6830: Denial of service in Modicon M580

> An attacker can cause a denial of service on Schneider Electric Modicon M580 controllers by sending a specifically timed HTTP request.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xjgc-mvgw-p5qh

## What is CVE-2019-6830?

CVE-2019-6830 is a medium-severity denial of service vulnerability in Schneider Electric SE Modicon M580, published on 17 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A CWE-248: Uncaught Exception vulnerability exists IN Modicon M580 all versions prior to V2.80, which could cause a possible denial of service when sending an appropriately timed HTTP request to the controller.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-248 (Uncaught Exception)

## Which versions are affected by CVE-2019-6830?

It affects 1 product.


Products: Schneider-Electric Modicon M580 Firmware.

## How do I fix CVE-2019-6830?

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

## Is CVE-2019-6830 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6830 and fix it if it is affected.

What it is: CVE-2019-6830 is a medium-severity denial of service vulnerability in Schneider Electric SE Modicon M580, published on 17 Sep 2019. 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-2019-6830 in the wild and no public exploit code.

Affected product: Schneider Electric SE Modicon M580. 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-2019-6830/ (Markdown: https://insights.sbomify.com/CVE-2019-6830/index.md)
```

## Sources

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

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