dbcve.org
Cps Mg341 Adsc1 111 FirmwareOperating system · Contec

CVE-2023-27389

HIGH · 7.2 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to after 3.7.10 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Inadequate encryption strength vulnerability in the firmware update mechanism of CONPROSYS IoT Gateway products. A remote authenticated attacker with administrative privileges can upload a specially crafted firmware update file that, due to weak encryption protection, allows altering device information, causing denial-of-service, or executing arbitrary code on the affected devices.

MitigationUpdate firmware to versions beyond the vulnerable releases (Ver.3.7.10 for M2M Gateway, Ver.3.7.6 for M2M Controller Integrated Type, Ver.3.8.8 for M2M Controller Configurable Type). If patches are unavailable, strictly limit administrative access to trusted personnel and implement network segmentation to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cps Mg341 Adsc1 111 FirmwareOperating system
Affected:<= 3.7.10
Cps Mg341 Adsc1 931 FirmwareOperating system
Affected:<= 3.7.10
Cps Mg341g Adsc1 111 FirmwareOperating system
Affected:<= 3.7.10
Cps Mg341g Adsc1 930 FirmwareOperating system
Affected:<= 3.7.10
Cps Mg341g5 Adsc1 931 FirmwareOperating system
Affected:<= 3.7.10
Cps Mc341 Adsc1 111 FirmwareOperating system
Affected:<= 3.7.6
Cps Mc341 Adsc1 931 FirmwareOperating system
Affected:<= 3.7.6
Cps Mc341 Adsc2 111 FirmwareOperating system
Affected:<= 3.7.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Locate the product label or access the device web interface to confirm the exact model number (e.g., CPS-MC341, CPS-MG341, CPS-MG341G, CPS-MG341G5) and variant (111, 930, 931).
    Affected if The model is one of: CPS-MC341 (any variant), CPS-MG341, CPS-MG341G, or CPS-MG341G5.
  2. Check the installed firmware version
    Access the device administrative web interface and navigate to the system information or firmware version page. Alternatively, check the device documentation or management console for the current firmware version.
    Affected if The firmware version is 3.7.10 or lower for MG341 series, or 3.7.6 or lower for MC341 series.
  3. Verify firmware update functionality is accessible
    Check if the device web interface includes a firmware update or firmware upload feature. Confirm the URL or menu path used for firmware updates.
    Affected if The firmware update mechanism is accessible and exposed on the device.
  4. Assess administrative access exposure
    Determine if the device administrative interface (web GUI) is accessible from untrusted networks. Check firewall rules, exposed IPs, or VPN requirements for administrative access.
    Affected if The administrative interface is accessible from the internet or untrusted network segments without proper access controls.

A user is affected if they have a CPS-MC341 or CPS-MG341 series device running firmware version 3.7.10 or lower (MG341 series) or 3.7.6 or lower (MC341 series), and the administrative interface is accessible for firmware upload operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.7.10
Interim mitigation

Update firmware to versions beyond the vulnerable releases (Ver.3.7.10 for M2M Gateway, Ver.3.7.6 for M2M Controller Integrated Type, Ver.3.8.8 for M2M Controller Configurable Type). If patches are unavailable, strictly limit administrative access to trusted personnel and implement network segmentation to reduce attack surface.

Recommended fix High confidence

M2M Gateway models: firmware >= 3.7.11; M2M Controller models: firmware >= 3.7.7

  1. 1. Identify the exact model number of the CONPROSYS device from the affected products list (CPS-MG341-ADSC1-111, CPS-MG341-ADSC1-931, CPS-MG341G-ADSC1-111, CPS-MG341G-ADSC1-930, CPS-MG341G5-ADSC1-931, CPS-MC341-ADSC1-111, CPS-MC341-ADSC1-931, CPS-MC341-ADSC2-111)
  2. 2. Navigate to the official CONTEC support website (www.contec.com) to download firmware updates
  3. 3. For M2M Gateway models (CPS-MG341 series): Download firmware version 3.7.11 or later
  4. 4. For M2M Controller Integrated Type models (CPS-MC341 series): Download firmware version 3.7.7 or later
  5. 5. Review the firmware upgrade instructions in the product manual before applying the update
  6. 6. Apply the firmware update file through the device's administrative web interface
  7. 7. After updating, verify the firmware version has been successfully upgraded and confirm the device is operational
Caveat Firmware updates may require device downtime; ensure backup of configuration before upgrading; verify compatibility with connected systems after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cps Mg341 Adsc1 111 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27389 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-27389 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data