CVE-2013-2793
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 · uneditedTriangle 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 remote attackers to cause a denial of service (infinite loop) via a crafted DNP3 TCP 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 · moderate confidenceA denial of service vulnerability exists in Triangle MicroWorks SCADA Data Gateway, DNP3 .NET Protocol components, and DNP3 C libraries. Attackers can send a crafted DNP3 TCP packet that triggers an infinite loop in the parsing logic, causing the affected component to become unresponsive.
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= 3.06.0.171= 3.15.0.369= 3.06.0000= 3.15.0000= 2.50= 2.50.0309= 3.00.0616CVSS 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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Triangle MicroWorks components in useReview installed software or application dependencies for Triangle MicroWorks DNP3 .NET components, ANSI C libraries, or SCADA Data Gateway. Check program files, application manifests, or dependency lists for tmw/dnp3 related DLLs (e.g., Tmw.DNP3.dll, Tmw.SCADA.DNP3.dll) or binaries (e.g., scadadatagateway.exe).Affected if Any Triangle MicroWorks DNP3 component is present in the environment
-
Check installed version of .NET Protocol ComponentsFor .NET components, right-click the DLL file in Windows Explorer, select Properties, then Details to view the File Version. Alternatively, check the version in the project references or assembly info if this is a compiled application.Affected if Version is 3.06.0.171 through 3.15.0.369 (inclusive)
-
Check installed version of ANSI C Source LibrariesInspect header files or library files for version strings. Check source code repositories or build configurations for version defines (often found in version.h or similar). Check compiled binaries for embedded version metadata.Affected if Version is 3.06.0000 through 3.15.0000 (inclusive)
-
Check installed version of SCADA Data GatewayOpen the SCADA Data Gateway application or service, then navigate to Help > About or check the installation directory for version information in the executable or configuration files.Affected if Version is 2.50, 2.50.0309, or 3.00.0616
-
Verify DNP3 protocol handling is activeCheck if the component is configured to process DNP3 traffic. For SCADA Data Gateway, review configuration files for enabled DNP3 listeners or masters. For .NET/C libraries, verify if application code initializes DNP3 protocol handlers.Affected if DNP3 protocol processing is enabled and the component is accepting DNP3 TCP connections
The environment is affected if any Triangle MicroWorks DNP3 component with a version in the affected ranges is installed and configured to process DNP3 protocol traffic.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied patches for affected versions or upgrade to a patched release. Until patched, restrict network access to DNP3 services using firewalls or network segmentation to minimize exposure to untrusted networks.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2793 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-2793 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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