# CVE-2013-0664: Command injection in n/a

> Authenticated remote attackers can execute arbitrary code on Schneider Electric PLC modules by embedding Modbus messages in SOAP requests.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **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-rvwq-pwvv-r8jc

## What is CVE-2013-0664?

CVE-2013-0664 is a high-severity command injection 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 FactoryCast service on the Schneider Electric Quantum 140NOE77111 and 140NWM10000, M340 BMXNOE0110x, and Premium TSXETY5103 PLC modules allows remote authenticated users to send Modbus messages, and consequently execute arbitrary code, by embedding these messages in SOAP HTTP POST requests.

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

It affects 3 products.


Products: Schneider-Electric Modicon M340, Schneider-Electric Modicon Premium, Schneider-Electric Modicon Quantum Plc.

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

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

## Is CVE-2013-0664 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0663](https://insights.sbomify.com/CVE-2013-0663/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-2761](https://insights.sbomify.com/CVE-2013-2761/): Denial of service in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0664 is a high-severity command injection 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-0664 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-0664/ (Markdown: https://insights.sbomify.com/CVE-2013-0664/index.md)
```

## Sources

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

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