# CVE-2013-2793: Denial of service in n/a

> Remote attackers can cause a denial of service via infinite loop in SCADA Data Gateway and DNP3 components using crafted TCP packets.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3548-54w8-x56q

## What is CVE-2013-2793?

CVE-2013-2793 is a high-severity denial of service vulnerability in n/a, published on 9 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 remote attackers to cause a denial of service (infinite loop) via a crafted DNP3 TCP packet.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2013-2793?

It affects 3 products.


Products: Trianglemicroworks .Net Communication Protocol Components, Trianglemicroworks Ansi C Source Code Libraries, Trianglemicroworks Scada Data Gateway.

## How do I fix CVE-2013-2793?

No fix has been published for CVE-2013-2793 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-2793 being exploited?

There is no known exploitation of CVE-2013-2793 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-2794](https://insights.sbomify.com/CVE-2013-2794/): Denial of service in n/a (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2793 and fix it if it is affected.

What it is: CVE-2013-2793 is a high-severity denial of service vulnerability in n/a, published on 9 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2793 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-2793/ (Markdown: https://insights.sbomify.com/CVE-2013-2793/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2793
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2793
- OSV: https://osv.dev/vulnerability/CVE-2013-2793

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-2793/
Summaries are generated and may contain mistakes; the official description above is the record.