CVE-2019-6849
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-200: Information Exposure vulnerability exists in Modicon M580, Modicon BMENOC 0311, and Modicon BMENOC 0321, which could cause the disclosure of sensitive information when using specific Modbus services provided by 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 confidenceThis is an information disclosure vulnerability (CWE-200) affecting Schneider Electric Modicon M580 PLCs and BMENOC 0311/0321 communication modules. The REST API exposes sensitive information through specific Modbus services, allowing unauthorized users to access sensitive data via the web interface.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device model and firmware versionAccess the PLC or communication module through its web interface or use Schneider Electric diagnostic tools to confirm the exact model number (Modicon M580, BMENOC 0311, or BMENOC 0321) and installed firmware versionAffected if The device is a Modicon M580, BMENOC 0311, or BMENOC 0321 with any firmware version
-
Verify the REST API is accessibleAttempt to access the web interface via HTTP/HTTPS on the device's IP address. Check if the REST API endpoints respond (typically at /api/ or similar paths)Affected if The REST API is exposed and responds to HTTP/HTTPS requests from your observation point
-
Check for unauthenticated Modbus service accessQuery the REST API for Modbus-related endpoints (such as /api/modbus or similar paths) using a web browser or HTTP client without providing credentialsAffected if Sensitive Modbus service data is returned without requiring authentication
-
Inspect web server access logs for Modbus queriesReview the device's web server access logs (if accessible) or upstream firewall/proxy logs for unusual queries to Modbus-related API endpoints from unauthorized IP addressesAffected if Logs show requests to Modbus API endpoints originating from unexpected or unauthorized sources
Your environment is affected if you have any Modicon M580, BMENOC 0311, or BMENOC 0321 devices with their REST API web interface exposed and accessible, as all firmware versions of these products contain the vulnerability.
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 dataRestrict network access to the REST API using network segmentation and firewall rules; apply any available vendor patches; if no patch exists, monitor access logs for suspicious Modbus service queries.
- 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-6849 — 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-6849 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