CVE-2023-28713
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 · uneditedPlaintext storage of a password exists in CONPROSYS HMI System (CHS) versions prior to 3.5.3. Because account information of the database is saved in a local file in plaintext, a user who can access the PC where the affected product is installed can obtain the information. As a result, information in the database 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 confidenceCONPROSYS HMI System (CHS) versions prior to 3.5.3 store database account credentials in plaintext within a local configuration file on the system. Any local user with file system access to the affected PC can read this file and obtain the plaintext database credentials, potentially allowing unauthorized access to and manipulation of the database.
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< 3.5.3CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm CONPROSYS HMI System installationLocate the Conprosys HMI System installation directory on the system, typically found under the program files or Contec installation folder.Affected if The product is not installed or the installation directory cannot be located.
-
Identify installed CHS versionAccess the program information or about section within the CHS application, or check the version metadata of the installed executable files.Affected if The installed version is any version prior to 3.5.3.
-
Locate configuration directoryNavigate to the CHS configuration directory within the installation folder, which contains configuration files for system settings and database connections.Affected if The configuration directory does not exist or cannot be accessed.
-
Find database configuration fileSearch for configuration files that store database connection parameters such as database name, username, and password.Affected if No database-related configuration file is found in the configuration directory.
-
Inspect credentials for plaintext storageOpen the database configuration file using a text editor or command to view its contents. Look for fields labeled password or similar that contain unmasked, plaintext credential strings.Affected if Database credentials are visible in plaintext within the configuration file, allowing any local user with file access to read them.
A user is affected if CONPROSYS HMI System is installed with a version prior to 3.5.3 and a database configuration file contains plaintext credentials accessible to local users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.5.3
Upgrade to CHS version 3.5.3 or later to obtain the patched version. Additionally, restrict file system permissions on the configuration directory to limit local user access to sensitive configuration files containing credentials.
CONPROSYS HMI System 3.5.3
- Upgrade CONPROSYS HMI System (CHS) to version 3.5.3 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28713 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28713 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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