# CVE-2019-6819: Denial of service in Modicon Controllers, Modicon M340 - firmware versions prior to V3.01 Modicon M580 - firmware versions prior to V2.80 All firmware versions of Modicon Quantum and Modicon Premium

> Attackers can cause a denial of service on Schneider Modicon controllers by sending specific Modbus frames, impacting industrial control system availability.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 22 May 2019
- **Updated:** 29 May 2026
- **Also known as:** GHSA-vf99-3r9r-pp36

## What is CVE-2019-6819?

CVE-2019-6819 is a high-severity denial of service vulnerability in Modicon Controllers, Modicon M340 - firmware versions prior to V3.01 Modicon M580 - firmware versions prior to V2.80 All firmware versions of Modicon Quantum and Modicon Premium, published on 22 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A CWE-754: Improper Check for Unusual or Exceptional Conditions vulnerability exists which could cause a possible Denial of Service when specific Modbus frames are sent to the controller in the products: Modicon M340 - firmware versions prior to V3.01, Modicon M580 - firmware versions prior to V2.80, All firmware versions of Modicon Quantum and Modicon Premium.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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

It affects 4 products.


Products: Schneider-Electric Modicon M340 Firmware, Schneider-Electric Modicon M580 Firmware, Schneider-Electric Modicon Premium Firmware, Schneider-Electric Modicon Quantum Firmware.

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

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

## Is CVE-2019-6819 being exploited?

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

## Other vulnerabilities in Modicon Controllers, Modicon M340 - firmware versions prior to V3.01 Modicon M580 - firmware versions prior to V2.80 All firmware versions of Modicon Quantum and Modicon Premium

- [CVE-2018-7842](https://insights.sbomify.com/CVE-2018-7842/): Auth bypass in Modicon M580 Modicon M340 Modicon Quantum Modicon Premium (critical 9.8)
- [CVE-2018-7846](https://insights.sbomify.com/CVE-2018-7846/): Auth bypass in Modicon M580 Modicon M340 Modicon Quantum Modicon Premium (critical 9.8)
- [CVE-2018-7847](https://insights.sbomify.com/CVE-2018-7847/): Missing authorization in Modicon M580 Modicon M340 Modicon Quantum Modicon Premium (critical 9.8)
- [CVE-2019-6808](https://insights.sbomify.com/CVE-2019-6808/): Missing authorization in Modicon M580 Modicon M340 Modicon Quantum Modicon Premium (critical 9.8)
- [CVE-2019-6845](https://insights.sbomify.com/CVE-2019-6845/): Information disclosure in Modicon M580, Modicon M340, Modicon Premium , Modicon Quantum (all firmware versions) (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6819 is a high-severity denial of service vulnerability in Modicon Controllers, Modicon M340 - firmware versions prior to V3.01 Modicon M580 - firmware versions prior to V2.80 All firmware versions of Modicon Quantum and Modicon Premium, published on 22 May 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-6819 in the wild and no public exploit code.

Affected product: Modicon Controllers, Modicon M340 - firmware versions prior to V3.01 Modicon M580 - firmware versions prior to V2.80 All firmware versions of Modicon Quantum and Modicon Premium. 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-6819/ (Markdown: https://insights.sbomify.com/CVE-2019-6819/index.md)
```

## Sources

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

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