Scada Data GatewayApplication · Trianglemicroworks

CVE-2014-2342

MEDIUM · 5.0 CVSS v2.0 Published 2014-05-30
Fix available
A fix is available. Upgrade to after 3.00.0633 or later.
See remediation →
59/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 before 3.00.0635 allows remote attackers to cause a denial of service (excessive data processing) via a crafted DNP3 packet.

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 versions before 3.00.0635 are vulnerable to a denial of service attack. Remote attackers can send crafted DNP3 packets that trigger excessive data processing, causing the gateway to become unavailable.

MitigationUpgrade to Triangle MicroWorks SCADA Data Gateway version 3.00.0635 or later. Apply network segmentation and filtering to restrict unauthorized DNP3 traffic from untrusted networks.

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:<= 3.00.0633= 2.50= 2.50.0309= 2.51= 2.53= 2.54.0515= 2.54.0516= 2.54.0517= 2.54.0518= 2.54.0528= 2.54.0529= 2.54.0536

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 if Triangle MicroWorks SCADA Data Gateway is installed
    Check program files or application directories for 'Triangle MicroWorks' or 'Scada Data Gateway' folders. On Windows, review installed programs via Control Panel > Programs and Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion'
    Affected if The application is present on the system
  2. Determine the installed version
    Locate the version information in the application directory, registry keys, or by right-clicking the executable and selecting Properties > Details. Common locations include the main gateway executable or a versioninfo file within the application folder
    Affected if The version number matches any of the affected versions: <= 3.00.0633, or specifically 2.50, 2.50.0309, 2.51, 2.53, 2.54.0515, 2.54.0516, 2.54.0517, 2.54.0518, 2.54.0528, 2.54.0529, or 2.54.0536
  3. Verify DNP3 protocol handling is enabled
    Review the gateway configuration files or management interface for DNP3 listener/service settings. Check if the gateway is configured to accept DNP3 connections on the configured ports (typically UDP/TCP port 20000)
    Affected if DNP3 protocol processing is enabled and the gateway is listening for DNP3 traffic
  4. Assess network exposure of the DNP3 service
    Review firewall rules and network ACLs to determine if the DNP3 ports (default 20000) are accessible from untrusted networks. Use 'netstat -an | grep 20000' or equivalent to confirm listening status and bound interfaces
    Affected if The DNP3 service is bound to accessible network interfaces and exposed to untrusted networks

You are affected if Triangle MicroWorks SCADA Data Gateway is installed with a version <= 3.00.0633 or matching one of the specific affected versions, and DNP3 protocol handling is enabled and network-accessible.

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
Upgrade available Upgrade to a release after 3.00.0633
Interim mitigation

Upgrade to Triangle MicroWorks SCADA Data Gateway version 3.00.0635 or later. Apply network segmentation and filtering to restrict unauthorized DNP3 traffic from untrusted networks.

Fix this in Scada Data Gateway Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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