# CVE-2023-27389: Weak cryptography in CONPROSYS IoT Gateway products

> Remote authenticated administrators can exploit weak encryption to upload malicious firmware, leading to arbitrary code execution or denial of service.

- **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:** 11 Apr 2023
- **Updated:** 10 Feb 2025
- **Also known as:** GHSA-88r9-vcj8-625f

## What is CVE-2023-27389?

CVE-2023-27389 is a high-severity vulnerability in Contec CO.,LTD. CONPROSYS IoT Gateway products, published on 11 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Inadequate encryption strength vulnerability in CONPROSYS IoT Gateway products allows a remote authenticated attacker with an administrative privilege to apply a specially crafted Firmware update file, alter the information, cause a denial-of-service (DoS) condition, and/or execute arbitrary code. The affected products and versions are as follows: M2M Gateway with the firmware Ver.3.7.10 and earlier (CPS-MG341-ADSC1-111, CPS-MG341-ADSC1-931, CPS-MG341G-ADSC1-111, CPS-MG341G-ADSC1-930, and CPS-MG341G5-ADSC1-931), M2M Controller Integrated Type with firmware Ver.3.7.6 and earlier versions (CPS-MC341-ADSC1-111, CPS-MC341-ADSC1-931, CPS-MC341-ADSC2-111, CPS-MC341G-ADSC1-110, CPS-MC341Q-ADSC1-111, CPS-MC341-DS1-111, CPS-MC341-DS11-111, CPS-MC341-DS2-911, and CPS-MC341-A1-111), and M2M Controller Configurable Type with firmware Ver.3.8.8 and earlier versions (CPS-MCS341-DS1-111, CPS-MCS341-DS1-131, CPS-MCS341G-DS1-130, CPS-MCS341G5-DS1-130, and CPS-MCS341Q-DS1-131).

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2023-27389?

It affects 19 products.


Products: Contec Cps-Mc341-A1-111 Firmware, Contec Cps-Mc341-Adsc1-111 Firmware, Contec Cps-Mc341-Adsc1-931 Firmware, Contec Cps-Mc341-Adsc2-111 Firmware, Contec Cps-Mc341-Ds1-111 Firmware, Contec Cps-Mc341-Ds11-111 Firmware, Contec Cps-Mc341-Ds2-911 Firmware, Contec Cps-Mc341g-Adsc1-110 Firmware, Contec Cps-Mc341q-Adsc1-111 Firmware, Contec Cps-Mcs341-Ds1-111 Firmware, Contec Cps-Mcs341-Ds1-131 Firmware, Contec Cps-Mcs341g-Ds1-130 Firmware, Contec Cps-Mcs341g5-Ds1-130 Firmware, Contec Cps-Mcs341q-Ds1-131 Firmware, Contec Cps-Mg341-Adsc1-111 Firmware, Contec Cps-Mg341-Adsc1-931 Firmware, Contec Cps-Mg341g-Adsc1-111 Firmware, Contec Cps-Mg341g-Adsc1-930 Firmware, Contec Cps-Mg341g5-Adsc1-931 Firmware.

## How do I fix CVE-2023-27389?

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

## Is CVE-2023-27389 being exploited?

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

## Other vulnerabilities in Contec CO.,LTD. CONPROSYS IoT Gateway products

- [CVE-2023-27917](https://insights.sbomify.com/CVE-2023-27917/): Command injection in CONPROSYS IoT Gateway products (high 8.8)
- [CVE-2023-23575](https://insights.sbomify.com/CVE-2023-23575/): Missing authorization in CONPROSYS IoT Gateway products (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27389 and fix it if it is affected.

What it is: CVE-2023-27389 is a high-severity vulnerability in Contec CO.,LTD. CONPROSYS IoT Gateway products, published on 11 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-27389 in the wild and no public exploit code.

Affected product: Contec CO.,LTD. CONPROSYS IoT Gateway products. 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-2023-27389/ (Markdown: https://insights.sbomify.com/CVE-2023-27389/index.md)
```

## Sources

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

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