CVE-2019-6810
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 · uneditedCWE-284: Improper Access Control vulnerability exists in BMXNOR0200H Ethernet / Serial RTU module (all firmware versions), which could cause the execution of commands by unauthorized users when using IEC 60870-5-104 protocol.
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 confidenceImproper Access Control vulnerability in Schneider Electric BMXNOR0200H RTU module allows unauthorized command execution via the IEC 60870-5-104 protocol across all firmware versions.
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 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 BMXNOR0200H RTU module in asset inventoryReview network topology and asset management systems for Schneider Electric BMXNOR0200H Remote Terminal Units. Check device nameplates, SNMP sysDescr responses, or management interfaces for the exact model identifier BMXNOR0200H.Affected if The BMXNOR0200H RTU module is present in the environment.
-
Verify firmware versionAccess the device web interface, console, or management software and retrieve the firmware version. Common paths: Device Info menu, System Settings, or CLI command 'show version'. Compare against the affected range.Affected if The device is running any firmware version (all versions are affected per CVE-2019-6810).
-
Confirm IEC 60870-5-104 protocol is enabledCheck device configuration settings for IEC 60870-5-104 protocol configuration. Look for protocol enable/disable toggles, port 2404 (standard 104 port) listener status, or protocol-specific access control lists.Affected if The IEC 60870-5-104 protocol is enabled and configured on the device.
-
Assess network exposure of IEC 104 trafficReview firewall rules, network segmentation, and ACLs governing traffic to and from the BMXNOR0200H on port 2404/TCP. Determine if the protocol interface is accessible from untrusted networks or the internet.Affected if The IEC 60870-5-104 interface is accessible from untrusted or external networks without proper network segmentation or access controls.
A user is affected if a BMXNOR0200H RTU module with IEC 60870-5-104 protocol enabled is present and exposed to untrusted network segments.
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 dataImplement network segmentation and access controls to limit IEC 60870-5-104 protocol exposure; contact Schneider Electric for firmware update when available.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6810 — 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-6810 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