Conprosys Hmi SystemApplication · Contec

CVE-2023-28657

HIGH · 8.8 CVSS v3.1 Published 2023-06-01
Fix available
A fix is available. Upgrade to 3.5.3 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
Improper access control vulnerability exists in CONPROSYS HMI System (CHS) versions prior to 3.5.3. A user of the PC where the affected product is installed may gain an administrative privilege. As a result, information regarding the product may be obtained and/or altered by the user.

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

This is a local privilege escalation vulnerability in CONPROSYS HMI System (CHS). A local user on the PC where the affected product is installed can gain administrative privileges due to improper access controls, allowing them to obtain or alter product information.

MitigationUpgrade CONPROSYS HMI System to version 3.5.3 or later to remediate this vulnerability.

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
Conprosys Hmi SystemApplication
Affected:< 3.5.3

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. Check if CONPROSYS HMI System is installed
    Look for the product in the Windows Add/Remove Programs list, or check common installation directories such as C:\Program Files\CONPROSYS or C:\Program Files (x86)\CONPROSYS for the CHS application folders
    Affected if The product is found installed on the system
  2. Identify the installed version of CONPROSYS HMI System
    Check the program version information. In Windows, right-click the executable (typically named CHS.exe or similar in the installation folder), select Properties, and view the Details tab for the Version field. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry related to Conprosys HMI System and review the DisplayVersion value
    Affected if The displayed version number is lower than 3.5.3 or the version cannot be determined but the product is present
  3. Verify the service or process status
    Open Task Manager or Services.msc and look for a running service or process associated with CONPROSYS HMI System (often named conprosys_hmi, CHS, or similar). Also check for any HMI-related services running under a local or system account
    Affected if The CONPROSYS HMI System service or process is running on the system and the version is below 3.5.3

If CONPROSYS HMI System is installed and the version is identified as less than 3.5.3, the environment is affected by this local privilege escalation vulnerability.

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 3.5.3 or later
Fixed in 3.5.3
Interim mitigation

Upgrade CONPROSYS HMI System to version 3.5.3 or later to remediate this vulnerability.

Recommended fix High confidence

Conprosys HMI System version 3.5.3

  1. Upgrade CONPROSYS HMI System to version 3.5.3 or later
  2. Obtain the update from the official Contec download page at www.contec.com
  3. Apply the update following standard upgrade procedures for the CONPROSYS HMI System

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

Fix this in Conprosys Hmi System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-28657 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