# CVE-2012-3015: Privilege escalation in n/a

> Local attackers can gain privileges by placing a malicious DLL in a project folder, affecting Siemens SIMATIC STEP7 users.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Jul 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-jvr3-fqr5-pf4c

## What is CVE-2012-3015?

CVE-2012-3015 is a medium-severity vulnerability in n/a, published on 26 Jul 2012. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Untrusted search path vulnerability in Siemens SIMATIC STEP7 before 5.5 SP1, as used in SIMATIC PCS7 7.1 SP3 and earlier and other products, allows local users to gain privileges via a Trojan horse DLL in a STEP7 project folder.

## Which versions are affected by CVE-2012-3015?

It affects 2 products.


Products: Siemens Simatic Pcs7, Siemens Simatic Step 7.

## How do I fix CVE-2012-3015?

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

## Is CVE-2012-3015 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-8551](https://insights.sbomify.com/CVE-2014-8551/): Code injection in n/a (critical 10.0)
- [CVE-2013-3957](https://insights.sbomify.com/CVE-2013-3957/): SQL injection in n/a (high 7.5)
- [CVE-2013-3958](https://insights.sbomify.com/CVE-2013-3958/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2012-3032](https://insights.sbomify.com/CVE-2012-3032/): SQL injection in n/a (high 7.5)
- [CVE-2014-4686](https://insights.sbomify.com/CVE-2014-4686/): Hardcoded credentials in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-3015 and fix it if it is affected.

What it is: CVE-2012-3015 is a medium-severity vulnerability in n/a, published on 26 Jul 2012. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-3015 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-2012-3015/ (Markdown: https://insights.sbomify.com/CVE-2012-3015/index.md)
```

## Sources

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

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