dbcve.org
Scada Data GatewayApplication · Trianglemicroworks

CVE-2023-39465

HIGH · 7.5 CVSS v3.0 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Triangle MicroWorks SCADA Data Gateway Use of Hard-coded Cryptograhic Key Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Triangle MicroWorks SCADA Data Gateway. Authentication is not required to exploit this vulnerability. The specific flaw exists within the TmwCrypto class. The issue results from the usage of a hard-coded cryptograhic key and the usage of a hard-coded certificate. An attacker can leverage this vulnerability to disclose sensitive information. Was ZDI-CAN-20615.

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 hard-coded cryptographic key vulnerability in the TmwCrypto class of Triangle MicroWorks SCADA Data Gateway. The application uses a hard-coded cryptographic key AND a hard-coded certificate, which allows unauthenticated remote attackers to decrypt sensitive information. Since no authentication is required, attackers can directly exploit this to disclose sensitive data transmitted through or stored by the gateway.

MitigationReplace the hard-coded cryptographic key and certificate with dynamically generated, unique values; implement secure key management (e.g., secrets management solution, HSM, or encrypted configuration); rotate any exposed keys; and verify all encrypted data streams still function correctly after remediation.

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
Scada Data GatewayApplication
Affected:= 5.1.3.20324

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Verify installed version
    Locate the Triangle MicroWorks SCADA Data Gateway installation and check the product version (typically via installer, program properties, or registry entry). Compare your installed version to 5.1.3.20324.
    Affected if The installed version is exactly 5.1.3.20324
  2. Locate TmwCrypto configuration
    Search the application installation directory and configuration folders for files named TmwCrypto, crypto.config, or similar files containing cryptographic settings.
    Affected if A TmwCrypto configuration file exists and contains hard-coded key material
  3. Inspect certificate storage
    Examine the application data directory and installation folder for certificate files (typically .cer, .pem, .pfx, or .p12 extensions) that may be bundled with the application.
    Affected if Pre-installed certificate files exist in the application directory without user-generated certificates
  4. Review configuration files for embedded keys
    Open XML, INI, or config files in the application directory and search for suspicious cryptographic key values (look for long alphanumeric strings in key, cert, or crypto-related tags).
    Affected if Configuration files contain hard-coded cryptographic keys or certificate data rather than references to external secure storage

A user is affected if their installed SCADA Data Gateway version is exactly 5.1.3.20324 AND the application uses the bundled hard-coded cryptographic key and certificate in the TmwCrypto class.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the hard-coded cryptographic key and certificate with dynamically generated, unique values; implement secure key management (e.g., secrets management solution, HSM, or encrypted configuration); rotate any exposed keys; and verify all encrypted data streams still function correctly after remediation.

Fix this in Scada Data Gateway Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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