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

> Remote authenticated attackers can crash Schneider Electric M340 PLC modules by sending crafted FTP traffic, causing a denial of service.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-jv4v-gw8f-j23r

## What is CVE-2013-2761?

CVE-2013-2761 is a medium-severity denial of service vulnerability in n/a, published on 4 Apr 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Schneider Electric M340 BMXNOE01xx and BMXP3420xx PLC modules allow remote authenticated users to cause a denial of service (module crash) via crafted FTP traffic, as demonstrated by the FileZilla FTP client.

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

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

It affects 1 product.


Products: Schneider-Electric Modicon M340.

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

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

## Is CVE-2013-2761 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0664](https://insights.sbomify.com/CVE-2013-0664/): Command injection in n/a (high 8.5)
- [CVE-2013-0663](https://insights.sbomify.com/CVE-2013-0663/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2761 is a medium-severity denial of service vulnerability in n/a, published on 4 Apr 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2761 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-2761/ (Markdown: https://insights.sbomify.com/CVE-2013-2761/index.md)
```

## Sources

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

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