CVE-2019-6848
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-755: Improper Handling of Exceptional Conditions vulnerability exists in Modicon M580 CPU (BMEx58*) and Modicon M580 communication module (BMENOC0311, BMENOC0321) (see notification for version info), which could cause a Denial of Service attack on the PLC when sending specific data on the REST API of the controller/communication module.
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 confidenceA CWE-755 improper handling of exceptional conditions vulnerability exists in the REST API of Schneider Electric Modicon M580 CPU and communication modules. Sending specific malformed data to the REST API triggers an unhandled exception causing the PLC to crash and become unresponsive, resulting in a Denial of Service condition.
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 dataall versionsall versionsall versionsCVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Identify Schneider Electric Modicon M580 CPU in your environmentLocate PLC hardware by reviewing network documentation, asset inventories, or physically inspecting industrial control system cabinets for Modicon M580 CPU modules (model numbers typically include BMECPUxxxx)Affected if A Schneider Electric Modicon M580 CPU is present in the environment
-
Identify Bmenoc communication modulesReview network documentation, asset inventories, or physically inspect control system cabinets for Bmenoc 0311 or Bmenoc 0321 communication modulesAffected if A Bmenoc 0311 or Bmenoc 0321 module is present in the environment
-
Check if REST API is enabled on the deviceAccess the device web interface or consult configuration documentation to determine if the REST API service is running. On Modicon M580, this is typically available on port 502 or 8080 for HTTP accessAffected if The REST API service is enabled and accessible on the device
-
Assess network exposure of the REST APIReview firewall rules, network segmentation configurations, and ACLs to determine if the REST API ports (502/tcp, 8080/tcp, or vendor-specified ports) are accessible from untrusted networksAffected if The REST API is reachable from less trusted networks or directly from enterprise/IT networks
You are affected if you have a Modicon M580 CPU or a Bmenoc 0311/0321 communication module with the REST API enabled and network-accessible, since all firmware versions of these products are vulnerable.
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 dataApply the vendor-provided firmware patch to the Modicon M580 CPU and communication modules. If patching is immediately impractical, restrict network access to the REST API via firewalls or network segmentation to limit attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6848 — 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-6848 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