# CVE-2019-14926: Hardcoded credentials in n/a

> Hard-coded SSH keys in Mitsubishi ME-RTU devices allow attackers to gain unauthorized access and disclose encrypted data.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 28 Oct 2019
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-jv5q-xqwr-9h7w

## What is CVE-2019-14926?

CVE-2019-14926 is a critical vulnerability in n/a, published on 28 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Mitsubishi Electric Europe B.V. ME-RTU devices through 2.02 and INEA ME-RTU devices through 3.0. Hard-coded SSH keys allow an attacker to gain unauthorised access or disclose encrypted data on the RTU due to the keys not being regenerated on initial installation or with firmware updates. In other words, these devices use private-key values in /etc/ssh/ssh_host_rsa_key, /etc/ssh/ssh_host_ecdsa_key, and /etc/ssh/ssh_host_dsa_key files that are publicly available from the vendor web sites.

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

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

It affects 2 products.


Products: Inea Me-Rtu Firmware, Mitsubishielectric Smartrtu Firmware.

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

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

## Is CVE-2019-14926 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14929](https://insights.sbomify.com/CVE-2019-14929/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-14930](https://insights.sbomify.com/CVE-2019-14930/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-14931](https://insights.sbomify.com/CVE-2019-14931/): Command injection in n/a (critical 9.8)
- [CVE-2019-14927](https://insights.sbomify.com/CVE-2019-14927/): Information disclosure in n/a (high 7.5)
- [CVE-2019-14925](https://insights.sbomify.com/CVE-2019-14925/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14926 is a critical vulnerability in n/a, published on 28 Oct 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-14926 in the wild and no public exploit code.

Affected product: n/a. 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-14926/ (Markdown: https://insights.sbomify.com/CVE-2019-14926/index.md)
```

## Sources

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

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