dbcve.org
Scada Data GatewayApplication · Trianglemicroworks

CVE-2023-39457

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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 Missing Authentication Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of Triangle MicroWorks SCADA Data Gateway. Authentication is not required to exploit this vulnerability. The specific flaw exists due to the lack of user authentication. The issue results from missing authentication in the default system configuration. An attacker can leverage this vulnerability to execute arbitrary code in the context of root. Was ZDI-CAN-20501.

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

Missing authentication vulnerability in Triangle MicroWorks SCADA Data Gateway allows remote unauthenticated attackers to bypass authentication and execute arbitrary code as root due to the lack of user authentication in the default system configuration.

MitigationApply vendor patches immediately and implement network segmentation to limit exposure of the SCADA Data Gateway to untrusted networks until the patch is applied.

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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 installed version of Triangle MicroWorks SCADA Data Gateway
    Check the installed application version through the product's about dialog, help menu, or check the installation directory for version information files. This can typically be found in the program's main window under Help > About, or by examining the executable file properties.
    Affected if The installed version is exactly 5.1.3.20324
  2. Verify whether user authentication is enabled in the system configuration
    Access the SCADA Data Gateway administrative interface and navigate to the security or authentication settings panel. Check if user authentication is configured and enforced for accessing the gateway.
    Affected if User authentication is not enabled or is set to a disabled state in the default configuration
  3. Confirm the default configuration allows unauthenticated access
    Review the system's security configuration file or settings that control authentication requirements. Look for configuration parameters that govern whether authentication is required for gateway access.
    Affected if The system is configured to allow access without requiring user credentials in the default state
  4. Check if the web management interface is accessible without credentials
    Attempt to access the SCADA Data Gateway web interface from a remote location without providing any username or password. Observe whether the interface loads without authentication prompts.
    Affected if The web interface loads and allows full or partial access without requiring any authentication credentials

A system is affected if it is running Triangle MicroWorks SCADA Data Gateway version 5.1.3.20324 with user authentication disabled in the default configuration, allowing unauthenticated remote access.

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

Apply vendor patches immediately and implement network segmentation to limit exposure of the SCADA Data Gateway to untrusted networks until the patch is applied.

Fix this in Scada Data Gateway Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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