CVE-2019-6830
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn uncaught exception vulnerability (CWE-248) in Schneider Electric Modicon M580 PLCs (all versions prior to V2.80) allows remote attackers to cause denial of service by sending an appropriately timed HTTP request to the controller, triggering an unhandled exception.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.80CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Modicon M580 PLC modelIdentify the PLC model through the engineering workstation software (EcoStruxure Control Expert/Unity Pro) by reading the PLC configuration, or access the PLC's web interface if available, and verify the hardware model is Modicon M580.Affected if The device is not a Modicon M580 PLC.
-
Check firmware versionRead the firmware version from the PLC using EcoStruxure Control Expert (formerly Unity Pro) by accessing the PLC's system information, or via the web interface under the 'Overview' or 'System' section. Compare the version number to the affected range.Affected if The firmware version is less than 2.80 (e.g., 2.70, 2.60, etc.).
-
Verify HTTP web server is enabledCheck the PLC configuration in EcoStruxure Control Expert for the 'Web Server' or 'HTTP Server' module settings, or access the PLC's IP address via a web browser to confirm the web interface is responding.Affected if HTTP web server is enabled and responding on the PLC's IP address.
-
Review PLC event logs for unhandled exceptionsAccess the PLC's event logs through EcoStruxure Control Expert or the web interface (under 'Event Log' or 'Diagnostics') and look for recent exception, fault, or crash entries that coincide with HTTP requests.Affected if Event logs show unhandled exceptions or unexpected restarts with timestamps matching HTTP activity.
You are affected if you have a Modicon M580 PLC with firmware version below V2.80 and the HTTP web server feature is enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.80
Upgrade Modicon M580 firmware to version V2.80 or later to remediate the uncaught exception vulnerability. Follow ICS vendor update procedures including backup, testing in non-production environment, and planning appropriate maintenance windows.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6830 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-6830 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data