dbcve.org
Scada Data GatewayApplication · Trianglemicroworks

CVE-2023-39467

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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 certificate 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 configuration of certificate web directory. The issue results from the exposure of sensitive information in the application webroot. An attacker can leverage this vulnerability to disclose sensitive information. Was ZDI-CAN-20798.

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

Triangle MicroWorks SCADA Data Gateway exposes sensitive certificate files through a misconfigured web directory, allowing unauthenticated remote attackers to access certificate information via the application webroot. This is a web server configuration flaw where certificate files are stored in a publicly accessible location rather than being moved outside the web document root.

MitigationRelocate all sensitive certificate files outside the web server's document root and configure web server access controls to prevent unauthorized access to any remaining certificate-related paths. Alternatively, implement proper web.config or equivalent deny rules for the certificate directory.

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
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify installed SCADA Data Gateway version
    Check the application's About or Version information, typically found in the installation directory or the application's UI. Look for a file like version.txt, or check the executable properties of the main application binary.
    Affected if Installed version is exactly 5.1.3.20324
  2. Locate certificate files in web root
    Examine the web server's document root directory (commonly the 'web', 'www', or 'html' subfolder within the installation directory). Search for certificate files with extensions such as .cer, .crt, .pem, .pfx, or .p12.
    Affected if Certificate files exist within a directory that is served by the web server (web root)
  3. Verify web accessibility of certificate directory
    Attempt to access known certificate file paths via HTTP/HTTPS requests to the application's web interface. For example, try accessing paths like /certs/, /certificates/, or the actual certificate filename through a web browser or curl command.
    Affected if Certificate files are downloadable via HTTP/HTTPS without authentication
  4. Check web server configuration for certificate paths
    Review the web.config file or equivalent web server configuration in the web root directory. Look for any <location> or <handlers> sections that define access to certificate-related directories.
    Affected if No deny rules exist for certificate directories, or certificate files are stored inside the web root without restriction

You are affected if the installed version is exactly 5.1.3.20324 AND certificate files are stored within or accessible through the web server's document root.

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

Relocate all sensitive certificate files outside the web server's document root and configure web server access controls to prevent unauthorized access to any remaining certificate-related paths. Alternatively, implement proper web.config or equivalent deny rules for the certificate directory.

Fix this in Scada Data Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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