# CVE-2019-6812: Hardcoded credentials in Modicon RTU Module, BMX-NOR-0200H with firmware versions prior to V1.7 IR 19

> Hardcoded credentials in the FTP protocol allow attackers to access confidential data on the Modicon RTU Module.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hcfq-hxjc-5c2h

## What is CVE-2019-6812?

CVE-2019-6812 is a high-severity vulnerability in Modicon RTU Module, BMX-NOR-0200H with firmware versions prior to V1.7 IR 19, published on 22 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A CWE-798 use of hardcoded credentials vulnerability exists in BMX-NOR-0200H with firmware versions prior to V1.7 IR 19 which could cause a confidentiality issue when using FTP protocol.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Schneider-Electric Bmx-nor-0200h Firmware.

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

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

## Is CVE-2019-6812 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6812 is a high-severity vulnerability in Modicon RTU Module, BMX-NOR-0200H with firmware versions prior to V1.7 IR 19, published on 22 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6812 in the wild and no public exploit code.

Affected product: Modicon RTU Module, BMX-NOR-0200H with firmware versions prior to V1.7 IR 19. 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-6812/ (Markdown: https://insights.sbomify.com/CVE-2019-6812/index.md)
```

## Sources

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

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