dbcve.org
Cps Mg341 Adsc1 111 FirmwareOperating system · Contec

CVE-2023-27917

HIGH · 8.8 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to after 3.7.10 or later.
See remediation →
94/100
Remediation priority · Urgent
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
OS command injection vulnerability in CONPROSYS IoT Gateway products allows a remote authenticated attacker who can access Network Maintenance page to execute arbitrary OS commands with a root privilege. 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

OS command injection vulnerability in CONPROSYS IoT Gateway products. A remote authenticated attacker with access to the Network Maintenance page can execute arbitrary OS commands with root privilege due to insufficient input sanitization when processing user-supplied parameters.

MitigationUpdate firmware to versions beyond 3.7.10 for M2M Gateway, 3.7.6 for M2M Controller Integrated Type, and 3.8.8 for M2M Controller Configurable Type. Restrict access to the Network Maintenance page to trusted users only as an interim control.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 CONPROSYS device model
    Access the device web interface or check the product label to confirm the exact model number (e.g., CPS-MG341, CPS-MG341G, CPS-MC341)
    Affected if The device model is one of the affected variants: CPS-MG341, CPS-MG341G, CPS-MG341G5, or CPS-MC341 series
  2. Check the installed firmware version
    Log into the device web interface and navigate to the System Information or Firmware Update page to view 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 Network Maintenance page accessibility
    Check if the Network Maintenance page (or equivalent network configuration page) is accessible to authenticated users on the device web interface
    Affected if The Network Maintenance functionality is enabled and accessible to users with login credentials

A user is affected if they operate a vulnerable CONPROSYS device model with firmware at or below the affected version AND the Network Maintenance page is accessible to authenticated users on their network.

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 3.7.10 for M2M Gateway, 3.7.6 for M2M Controller Integrated Type, and 3.8.8 for M2M Controller Configurable Type. Restrict access to the Network Maintenance page to trusted users only as an interim control.

Recommended fix Moderate confidence

Firmware version > 3.7.10 for CPS-MG341 series, > 3.7.6 for CPS-MC341 series, or > 3.8.8 for CPS-MCS341 series (obtain latest available from contec.com)

  1. 1. Access the CONPROSYS device web interface
  2. 2. Navigate to the Network Maintenance page (the attack vector for this vulnerability)
  3. 3. Identify the current firmware version under system settings or firmware information
  4. 4. Download the latest firmware from the official Contec website (www.contec.com) for your specific model
  5. 5. Follow Contec's firmware upgrade procedure documented in the product manual
  6. 6. Verify the firmware upgrade was successful and the new version is installed
  7. 7. Confirm the Network Maintenance page is no longer accessible to unauthenticated or untrusted users
Caveat Firmware upgrades on industrial devices may reset configuration; backup current configuration before upgrading and re-apply 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
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27917 — 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-27917 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