# CVE-2017-9963: Cross-site request forgery in n/a

> An attacker can trick a legitimate user into performing state-changing actions on the Secure Gateway component via a malicious link.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vrwh-p7px-62mr

## What is CVE-2017-9963?

CVE-2017-9963 is a high-severity vulnerability in n/a, published on 12 Feb 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A cross-site request forgery vulnerability exists on the Secure Gateway component of Schneider Electric's PowerSCADA Anywhere v1.0 redistributed with PowerSCADA Expert v8.1 and PowerSCADA Expert v8.2 and Citect Anywhere version 1.0 for multiple state-changing requests. This type of attack requires some level of social engineering in order to get a legitimate user to click on or access a malicious link/site containing the CSRF attack.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Schneider-Electric Powerscada Anywhere.

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

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

## Is CVE-2017-9963 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9963 is a high-severity vulnerability in n/a, published on 12 Feb 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-9963 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-2017-9963/ (Markdown: https://insights.sbomify.com/CVE-2017-9963/index.md)
```

## Sources

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

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