# CVE-2019-6852: Hardcoded credentials in Modicon Controllers (M340 CPUs, M340 communication modules, Premium CPUs, Premium communication modules, Quantum CPUs, Quantum communication modules - see security notification for specific versions)

> Attackers can obtain hardcoded FTP credentials via the web server, enabling unauthorized access to Schneider Modicon controllers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2019
- **Updated:** 28 May 2026
- **Also known as:** GHSA-vhvr-vv9x-qw7q

## What is CVE-2019-6852?

CVE-2019-6852 is a high-severity vulnerability in Schneider Electric Modicon Controllers (M340 CPUs, M340 communication modules,  Premium CPUs, Premium communication modules, Quantum CPUs, Quantum communication modules - see security notification for specific versions), published on 20 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2019-6852?

It affects 10 products.


Products: Schneider-Electric 140 Cpu6x Firmware, Schneider-Electric 140 Noc 77101 Firmware, Schneider-Electric 140 Noc 78x00 Firmware, Schneider-Electric 140 Noe 771x1 Firmware, Schneider-Electric Bmx Noc 0401 Firmware, Schneider-Electric Bmx Noe 0100 Firmware, Schneider-Electric Bmx Noe 0110 Firmware, Schneider-Electric Bmx P34x Firmware, Schneider-Electric Tsx Ety X103 Firmware, Schneider-Electric Tsx P57x Firmware.

## How do I fix CVE-2019-6852?

No fix has been published for CVE-2019-6852 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-6852 being exploited?

There is no known exploitation of CVE-2019-6852 in the wild and no public exploit code.

## Other vulnerabilities in Schneider Electric Modicon Controllers (M340 CPUs, M340 communication modules,  Premium CPUs, Premium communication modules, Quantum CPUs, Quantum communication modules - see security notification for specific versions)

- [CVE-2019-6859](https://insights.sbomify.com/CVE-2019-6859/): Hardcoded credentials in Modicon Controllers (All versions of the following CPUs and Communication Module product references listed in the Security Notifications) (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6852 and fix it if it is affected.

What it is: CVE-2019-6852 is a high-severity vulnerability in Schneider Electric Modicon Controllers (M340 CPUs, M340 communication modules,  Premium CPUs, Premium communication modules, Quantum CPUs, Quantum communication modules - see security notification for specific versions), published on 20 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6852 in the wild and no public exploit code.

Affected product: Schneider Electric Modicon Controllers (M340 CPUs, M340 communication modules,  Premium CPUs, Premium communication modules, Quantum CPUs, Quantum communication modules - see security notification for specific versions). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-6852/ (Markdown: https://insights.sbomify.com/CVE-2019-6852/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-6852
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-6852
- OSV: https://osv.dev/vulnerability/CVE-2019-6852

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-6852/
Summaries are generated and may contain mistakes; the official description above is the record.