CVE-2019-6859
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-798: Use of Hardcoded Credentials vulnerability exists in Modicon Controllers (All versions of the following CPUs and Communication Module product references listed in the Security Notifications), which could cause the disclosure of FTP hardcoded credentials when using the Web server of the controller on an unsecure network.
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 · high confidenceHardcoded FTP credentials are embedded in the firmware of Modicon Controllers (specific CPU and Communication Module models). When the controller's web server is accessible on an unsecured network, these credentials can be discovered and exploited by attackers to gain unauthorized access.
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 versionsall versionsall versionsall 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 controller modelLocate the Schneider Electric controller model number on the physical device or in the device documentation/system inventoryAffected if The model matches Bmx P34x, Bmx Noe 0100, Bmx Noe 0110, Bmx Noc 0401, Tsx P57x, Tsx Ety X103, 140 Cpu6x, or 140 Noe 771x1
-
Confirm firmware versionAccess the controller management interface or use Schneider Electric configuration software to retrieve the installed firmware versionAffected if Any firmware version is installed on an affected model (all versions of these products are vulnerable)
-
Verify FTP service statusCheck the controller configuration or network services list to determine if FTP server functionality is enabledAffected if FTP is enabled and accessible on the controller
-
Assess web server network exposureDetermine if the controller web interface is reachable from network segments outside the trusted operational technology networkAffected if The web server is accessible from an unsecured or untrusted network
-
Check for unauthorized access indicatorsReview controller access logs for any login attempts using default or unknown credentials, or for unexpected configuration changesAffected if Evidence exists of unauthorized access or anomalous FTP/web login activity
If the controller is one of the affected models and has FTP or web services exposed to an untrusted network, the environment is likely affected by this 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 dataIsolate affected controllers on dedicated network segments/VLANs, restrict web server access through firewalls, and apply any vendor firmware updates. If possible, disable unused services like FTP. Consider implementing compensating controls until permanent remediation via firmware update is available.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6859 — 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-6859 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