# CVE-2017-9961: Code injection in ProFace GP-Pro EX

> An attacker with local access can execute arbitrary code by placing a malicious DLL/OCX file, forcing the application to load it.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 25 Sep 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9g55-3rhr-jqqq

## What is CVE-2017-9961?

CVE-2017-9961 is a high-severity code injection vulnerability in Schneider Electric SE ProFace GP-Pro EX, published on 25 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability exists in Schneider Electric's Pro-Face GP Pro EX version 4.07.000 that allows an attacker to execute arbitrary code. Malicious code installation requires an access to the computer. By placing a specific DLL/OCX file, an attacker is able to force the process to load arbitrary DLL and execute arbitrary code in the context of the process.

## Which versions are affected by CVE-2017-9961?

It affects 1 product.


Products: Schneider-Electric Pro-Face Gp Pro Ex.

## How do I fix CVE-2017-9961?

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

## Is CVE-2017-9961 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9961 and fix it if it is affected.

What it is: CVE-2017-9961 is a high-severity code injection vulnerability in Schneider Electric SE ProFace GP-Pro EX, published on 25 Sep 2017. 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-2017-9961 in the wild and no public exploit code.

Affected product: Schneider Electric SE ProFace GP-Pro EX. 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-2017-9961/ (Markdown: https://insights.sbomify.com/CVE-2017-9961/index.md)
```

## Sources

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

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