Skip to content
Fencer Intel
medium 4.9

CVE-2013-2794 json

Triangle MicroWorks SCADA Data Gateway 2.50.0309 through 3.00.0616, DNP3 .NET Protocol components 3.06.0.171 through 3.15.0.369, and DNP3 C…

published 13y ago modified 4mo ago also EUVD-2013-2733

cvss
4.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

Triangle MicroWorks SCADA Data Gateway 2.50.0309 through 3.00.0616, DNP3 .NET Protocol components 3.06.0.171 through 3.15.0.369, and DNP3 C libraries 3.06.0000 through 3.15.0000 allow physically proximate attackers to cause a denial of service (infinite loop) via crafted input over a serial line.

Is CVE-2013-2794 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-13-240-01 updated cvss 4.7

Triangle MicroWorks Improper Input Validation

  • Triangle MicroWorks DNP3 .NET Protocol components >=v3.06.0.171, <=v3.15.0.369 Triangle MicroWorks DNP3 ANSI C source code libraries >=v3.06.0000, <=v3.15.0000 Triangle MicroWorks SCADA Data Gateway >=v2.50.0309, <=v3.00.0616
    affected: mitigation “Release notes are found here: (http://www.trianglemicroworks.com/documents/sdnp_scl_whats_new.pdf)”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.9 AV:L/AC:L/Au:N/C:N/I:N/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.