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

> Remote attackers can cause a denial of service via crafted DNP3 packets in GE Proficy HMI/SCADA drivers, impacting industrial control system availability.

- **Severity:** High 7.1 (`AV:N/AC:M/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:** 22 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m2f4-q5fw-hf6w

## What is CVE-2013-2811?

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

### Official description

The (1) Catapult DNP3 I/O driver before 7.2.0.60 and the (2) GE Intelligent Platforms Proficy DNP3 I/O driver before 7.20k, as used in DNPDrv.exe (aka the DNP master station server) in GE Intelligent Platforms Proficy HMI/SCADA - CIMPLICITY and iFIX, allow remote attackers to cause a denial of service (infinite loop) via a crafted DNP3 TCP packet.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 4 products.


Products: Catapultsoftware Catapult Dnp3 I\/O Driver, Ge Intelligent Platforms Proficy Dnp3 I\/O Driver, Ge Intelligent Platforms Proficy Hmi\/Scada Cimplicity, Ge Intelligent Platforms Proficy Hmi\/Scada Ifix.

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

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

## Is CVE-2013-2811 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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