dbcve.org
Bmx P34x FirmwareOperating system · Schneider Electric

CVE-2019-6852

HIGH · 7.5 CVSS v3.1 Published 2019-11-20
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 Controllers (M340 CPUs, M340 communication modules, Premium CPUs, Premium communication modules, Quantum CPUs, Quantum communication modules - see security notification for specific versions), 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 confidence

Hardcoded FTP credentials are embedded in the web server functionality of Modicon M340, Premium, and Quantum controllers. When these controllers' web interfaces are accessible over unsecure networks, an attacker can intercept or extract these credentials to gain unauthorized access to the controller's FTP service.

MitigationIsolate affected controllers from untrusted networks using network segmentation and firewall rules. Apply vendor firmware updates when released to remove hardcoded credentials, and implement compensating controls such as VPN access for legitimate remote 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 data
Bmx P34x FirmwareOperating system
Affected:all versions
Bmx Noe 0100 FirmwareOperating system
Affected:all versions
Bmx Noe 0110 FirmwareOperating system
Affected:all versions
Bmx Noc 0401 FirmwareOperating system
Affected:all versions
Tsx P57x FirmwareOperating system
Affected:all versions
Tsx Ety X103 FirmwareOperating system
Affected:all versions
140 Cpu6x FirmwareOperating system
Affected:all versions
140 Noe 771x1 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 controller firmware version
    Access the controller's management interface or use the vendor's programming software (e.g., Unity Pro, EcoStruxure) to read the installed firmware version from the controller properties or system information. Compare this version against the list of affected products: Bmx P34x, Bmx Noe 0100, Bmx Noe 0110, Bmx Noc 0401, Tsx P57x, Tsx Ety X103, 140 Cpu6x, 140 Noe 771x1.
    Affected if The installed firmware is any version of the listed Schneider Electric Modicon M340, Premium, or Quantum controller families.
  2. Verify if the web server feature is enabled
    Log into the controller's web management interface (if accessible) or check the controller configuration via the programming software for web server settings. Look for web server enable/disable status in the network module configuration or controller properties.
    Affected if The web server functionality is enabled on the controller.
  3. Confirm the FTP service is exposed on the network
    Perform a network scan of the controller's IP address on TCP port 21 (FTP) using tools such as nmap (nmap -p 21 <controller_ip>) or netcat to determine if the FTP service is listening and accessible.
    Affected if TCP port 21 is open and responding on the controller's IP address.
  4. Assess network accessibility of web and FTP services
    Review network segmentation configurations, firewall rules, and ACLs to determine whether the controller's web interface (typically HTTP/HTTPS ports 80/443) and FTP service (port 21) are reachable from untrusted network segments or the internet. Use network scanning from an untrusted segment to verify accessibility.
    Affected if The controller's web interface or FTP service is reachable from untrusted networks, the DMZ, or the internet without proper network segmentation or firewall filtering.

If the controller runs any version of the listed firmware AND has its web server enabled with FTP service accessible from an untrusted network, the environment is affected by this hardcoded credential vulnerability.

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

Isolate affected controllers from untrusted networks using network segmentation and firewall rules. Apply vendor firmware updates when released to remove hardcoded credentials, and implement compensating controls such as VPN access for legitimate remote access.

Fix this in Bmx P34x Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6852 — 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-6852 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