# CVE-2013-2786: Privilege escalation in n/a

> Local attackers can escalate privileges by placing a Trojan horse executable in the weakly protected MiCOM S1 installation directory.

- **Severity:** Medium 6.6 (`AV:L/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j9pj-gj4w-cfc2

## What is CVE-2013-2786?

CVE-2013-2786 is a medium-severity vulnerability in n/a, published on 10 Jul 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Alstom Grid MiCOM S1 Agile before 1.0.3 and Alstom Grid MiCOM S1 Studio use weak permissions for the MiCOM S1 %PROGRAMFILES% directory, which allows local users to gain privileges via a Trojan horse executable file.

Weakness: CWE-264

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

It affects 2 products.


Products: Alstom Micom S1 Agile, Alstom Micom S1 Studio.

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

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

## Is CVE-2013-2786 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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