dbcve.org
Modicon M580 FirmwareOperating system · Schneider Electric

CVE-2019-6850

HIGH · 7.5 CVSS v3.1 Published 2019-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A CWE-200: Information Exposure vulnerability exists in Modicon M580, Modicon BMENOC 0311, and Modicon BMENOC 0321, which could cause the disclosure of sensitive information when reading specific registers with 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 confidence

This is an information exposure vulnerability (CWE-200) in Schneider Electric's Modicon M580 PLC and BMENOC communication modules. The REST API endpoint allows reading specific sensitive registers without proper authorization, exposing configuration or process data that should be protected.

MitigationRestrict network access to the controller's REST API through firewall rules or network segmentation, and implement proper authentication and authorization controls for API endpoints. Consult Schneider Electric for firmware updates addressing this vulnerability.

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
Modicon M580 FirmwareOperating system
Affected:all versions
Modicon Bmenoc 0311 FirmwareOperating system
Affected:all versions
Modicon Bmenoc 0321 FirmwareOperating system
Affected:all versions

CVSS 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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the PLC model and firmware version
    Access the PLC engineering software (Unity Pro, EcoStruxure, or equivalent) and look at the CPU module properties, or use Schneider Electric's diagnostic tools to query the device for its model number and firmware version. Check if the device is a Modicon M580, BMENOC 0311, or BMENOC 0321.
    Affected if The device is any Modicon M580, BMENOC 0311, or BMENOC 0321 with any firmware version - all versions are affected.
  2. Confirm REST API is enabled on the controller
    Check the PLC configuration or web server settings within the engineering software. Look for REST API, web services, or HTTP server configuration settings on the controller. Alternatively, attempt to access the device's web interface by navigating to its IP address in a browser.
    Affected if The REST API/web server is enabled and accessible on the network.
  3. Test for unauthenticated register access
    Using a web browser or HTTP client (curl, Postman), send a GET request to the REST API endpoint that reads holding registers, for example: http://<device_ip>/api/registers or similar endpoints that expose register data. Do not provide any authentication credentials.
    Affected if The request returns register data (configuration or process values) without requiring login or authentication.
  4. Inspect network exposure of the REST API
    Review firewall rules, network segments, and access control lists to determine if the controller's HTTP port (typically 80/443) is reachable from untrusted networks, DMZ, or the internet. Use network scanning tools to verify accessibility.
    Affected if The REST API port is open to untrusted networks or is reachable from outside the trusted operational technology network.

A user is affected if they have a Modicon M580 or BMENOC module with the REST API enabled and accessible, and the API returns sensitive register data without requiring authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the controller's REST API through firewall rules or network segmentation, and implement proper authentication and authorization controls for API endpoints. Consult Schneider Electric for firmware updates addressing this vulnerability.

Fix this in Modicon M580 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6850 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-6850 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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