# CVE-2019-18238: Information disclosure in Moxa ioLogik 2500 series firmware, Version 3.0 or lower, IOxpress configuration utility, Version 2.3.0 or lower

> Attackers can access administrative accounts by reading unencrypted configuration files in Moxa ioLogik devices and IOxpress utility.

- **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:** 26 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9g94-m2hg-vj88

## What is CVE-2019-18238?

CVE-2019-18238 is a high-severity vulnerability in Moxa ioLogik 2500 series firmware, Version 3.0 or lower, IOxpress configuration utility, Version 2.3.0 or lower, published on 26 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Moxa ioLogik 2500 series firmware, Version 3.0 or lower, and IOxpress configuration utility, Version 2.3.0 or lower, sensitive information is stored in configuration files without encryption, which may allow an attacker to access an administrative account.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 20 products.


Products: Moxa Iologik 2512-Hspa-T Firmware, Moxa Iologik 2512-Hspa Firmware, Moxa Iologik 2512-T Firmware, Moxa Iologik 2512-Wl1-Eu-T Firmware, Moxa Iologik 2512-Wl1-Eu Firmware, Moxa Iologik 2512-Wl1-Jp-T Firmware, Moxa Iologik 2512-Wl1-Jp Firmware, Moxa Iologik 2512-Wl1-Us-T Firmware, Moxa Iologik 2512-Wl1-Us Firmware, Moxa Iologik 2512 Firmware, Moxa Iologik 2542-Hspa-T Firmware, Moxa Iologik 2542-Hspa Firmware, Moxa Iologik 2542-T Firmware, Moxa Iologik 2542-Wl1-Eu-T Firmware, Moxa Iologik 2542-Wl1-Eu Firmware, Moxa Iologik 2542-Wl1-Jp-T Firmware, Moxa Iologik 2542-Wl1-Jp Firmware, Moxa Iologik 2542-Wl1-Us-T Firmware, Moxa Iologik 2542-Wl1-Us Firmware, Moxa Iologik 2542 Firmware.

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

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

## Is CVE-2019-18238 being exploited?

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

## Other vulnerabilities in Moxa ioLogik 2500 series firmware, Version 3.0 or lower, IOxpress configuration utility, Version 2.3.0 or lower

- [CVE-2019-18242](https://insights.sbomify.com/CVE-2019-18242/): Denial of service in Moxa ioLogik 2500 series firmware, Version 3.0 or lower, IOxpress configuration utility, Version 2.3.0 or lower (high 7.5)
- [CVE-2020-7003](https://insights.sbomify.com/CVE-2020-7003/): Information disclosure in Moxa ioLogik 2500 series firmware, Version 3.0 or lower, IOxpress configuration utility, Version 2.3.0 or lower (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-18238 is a high-severity vulnerability in Moxa ioLogik 2500 series firmware, Version 3.0 or lower, IOxpress configuration utility, Version 2.3.0 or lower, published on 26 Feb 2020. 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-18238 in the wild and no public exploit code.

Affected product: Moxa ioLogik 2500 series firmware, Version 3.0 or lower, IOxpress configuration utility, Version 2.3.0 or lower. 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-18238/ (Markdown: https://insights.sbomify.com/CVE-2019-18238/index.md)
```

## Sources

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

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