# CVE-2019-14927: Information disclosure in n/a

> Unauthenticated attackers can download configuration files containing sensitive credentials and data from Mitsubishi ME-RTU devices.

- **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:** 28 Oct 2019
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-xp5g-v8fx-97mv

## What is CVE-2019-14927?

CVE-2019-14927 is a high-severity 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. An unauthenticated remote configuration download vulnerability allows an attacker to download the smartRTU's configuration file (which contains data such as usernames, passwords, and other sensitive RTU data).

Weakness: CWE-425 (Direct Request), CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 2 products.


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

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

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

## Is CVE-2019-14927 being exploited?

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

Public exploit code:

- Mitsubishi Electric smartRTU / INEA ME-RTU - Unauthenticated Configuration Download (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2019-14926](https://insights.sbomify.com/CVE-2019-14926/): Hardcoded credentials in n/a (critical 9.8)
- [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-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-14927 and fix it if it is affected.

What it is: CVE-2019-14927 is a high-severity 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-14927 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-14927/ (Markdown: https://insights.sbomify.com/CVE-2019-14927/index.md)
```

## Sources

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

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