# CVE-2018-7241: Hardcoded credentials in Modicon Premium, Modicon Quantum, Modicon M340, BMXNOR0200

> Hardcoded accounts in Schneider Electric Modicon controllers allow attackers to gain unauthorized access and control over industrial systems.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rhfc-jm87-h52j

## What is CVE-2018-7241?

CVE-2018-7241 is a critical vulnerability in Schneider Electric SE Modicon Premium, Modicon Quantum, Modicon M340, BMXNOR0200, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hard coded accounts exist in Schneider Electric's Modicon Premium, Modicon Quantum, Modicon M340, and BMXNOR0200 controllers in all versions of the communication modules.

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

## Which versions are affected by CVE-2018-7241?

It affects 57 products.


Products: Schneider-Electric 140cpu31110 Firmware, Schneider-Electric 140cpu31110c Firmware, Schneider-Electric 140cpu43412u Firmware, Schneider-Electric 140cpu43412uc Firmware, Schneider-Electric 140cpu65150 Firmware, Schneider-Electric 140cpu65150c Firmware, Schneider-Electric 140cpu65160 Firmware, Schneider-Electric 140cpu65160c Firmware, Schneider-Electric 140cpu65160s Firmware, Schneider-Electric 140cpu65260 Firmware, Schneider-Electric 140cpu65260c Firmware, Schneider-Electric 140cpu65860 Firmware, Schneider-Electric 140cpu65860c Firmware, Schneider-Electric Bmxnor0200 Firmware, Schneider-Electric Bmxnor0200h Firmware, Schneider-Electric Modicon M340 Bmxp341000 Firmware, Schneider-Electric Modicon M340 Bmxp341000h Firmware, Schneider-Electric Modicon M340 Bmxp342000 Firmware, Schneider-Electric Modicon M340 Bmxp3420102 Firmware, Schneider-Electric Modicon M340 Bmxp3420102cl Firmware and 37 more.

## How do I fix CVE-2018-7241?

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

## Is CVE-2018-7241 being exploited?

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

## Other vulnerabilities in Schneider Electric SE Modicon Premium, Modicon Quantum, Modicon M340, BMXNOR0200

- [CVE-2018-7242](https://insights.sbomify.com/CVE-2018-7242/): Weak cryptography in Modicon Premium, Modicon Quantum, Modicon M340, BMXNOR0200 (critical 9.8)
- [CVE-2018-7760](https://insights.sbomify.com/CVE-2018-7760/): Auth bypass in Modicon M340, Modicon Premium, Modicon Quantum, BMXNOR0201 (critical 9.8)
- [CVE-2018-7761](https://insights.sbomify.com/CVE-2018-7761/): Code injection in Modicon M340, Modicon Premium, Modicon Quantum, BMXNOR0202 (critical 9.8)
- [CVE-2018-7240](https://insights.sbomify.com/CVE-2018-7240/): Command injection in Modicon Quantum (high 8.8)
- [CVE-2018-7759](https://insights.sbomify.com/CVE-2018-7759/): Memory corruption in Modicon M340, Modicon Premium, Modicon Quantum, BMXNOR0200 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7241 and fix it if it is affected.

What it is: CVE-2018-7241 is a critical vulnerability in Schneider Electric SE Modicon Premium, Modicon Quantum, Modicon M340, BMXNOR0200, published on 18 Apr 2018. 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-2018-7241 in the wild and no public exploit code.

Affected product: Schneider Electric SE Modicon Premium, Modicon Quantum, Modicon M340, BMXNOR0200. 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-2018-7241/ (Markdown: https://insights.sbomify.com/CVE-2018-7241/index.md)
```

## Sources

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

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