# CVE-2013-0655: Other in n/a

> Man-in-the-middle attackers can spoof software updates to execute arbitrary code on systems using the Schneider Electric Software Update Utility.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-8q56-7r9c-2j9q

## What is CVE-2013-0655?

CVE-2013-0655 is a critical vulnerability in n/a, published on 21 Jan 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The client in Schneider Electric Software Update (SESU) Utility 1.0.x and 1.1.x does not ensure that updates have a valid origin, which allows man-in-the-middle attackers to spoof updates, and consequently execute arbitrary code, by modifying the data stream on TCP port 80.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Schneider-Electric Software Update Utility.

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

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

## Is CVE-2013-0655 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-7799](https://insights.sbomify.com/CVE-2018-7799/): Code injection in Schneider Electric Software Update (SESU), all versions prior to V2.2.0 (high 7.8)
- [CVE-2020-7520](https://insights.sbomify.com/CVE-2020-7520/): Open redirect in Schneider Electric Software Update (SESU) V2.4.0 and prior. (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0655 is a critical vulnerability in n/a, published on 21 Jan 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0655 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-0655/ (Markdown: https://insights.sbomify.com/CVE-2013-0655/index.md)
```

## Sources

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

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