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

> Remote attackers can cause a networking outage on Tri Nano-10 PLC devices by sending crafted Modbus/TCP packets due to incorrect bounds checking.

- **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:** 10 Jul 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-x2jj-6rhr-24q9

## What is CVE-2013-2784?

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

### Official description

Triangle Research International (aka Tri) Nano-10 PLC devices with firmware before r81 use an incorrect algorithm for bounds checking of data in Modbus/TCP packets, which allows remote attackers to cause a denial of service (networking outage) via a crafted packet to TCP port 502.

Weakness: CWE-310

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

It affects 2 products.


Products: Triplc Nano-10 Plc, Triplc Nano-10 Plc Firmware.

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

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

## Is CVE-2013-2784 being exploited?

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

Public exploit code:

- Tri-PLC Nano-10 r81 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-5741](https://insights.sbomify.com/CVE-2013-5741/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2784 is a high-severity denial of service vulnerability in n/a, published on 10 Jul 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-2784 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-2784/ (Markdown: https://insights.sbomify.com/CVE-2013-2784/index.md)
```

## Sources

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

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