CVE-2017-9963
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in the Secure Gateway component of Schneider Electric's PowerSCADA Anywhere v1.0 and Citect Anywhere v1.0. The vulnerability allows attackers to trick authenticated users into unknowingly executing state-changing requests by embedding malicious requests in websites or links. Since the user is already authenticated to the application, the server processes these forged requests as legitimate, enabling unauthorized state modifications without direct server-side compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm PowerSCADA Anywhere or Citect Anywhere versionLocate the installed application and check its version number. This is typically found in the application itself, installation directory, or system information about installed software.Affected if The installed version is exactly 1.0 (PowerSCADA Anywhere v1.0 or Citect Anywhere v1.0)
-
Verify Secure Gateway web component is in useConfirm the web-based Secure Gateway interface is enabled and accessible. This is the component where the CSRF vulnerability exists.Affected if The Secure Gateway web interface is active and reachable on the network
-
Identify state-changing operationsReview the application's available functions and identify operations that modify state, such as configuration changes, user management, or control commands.Affected if The application exposes state-changing operations through its web interface
-
Inspect for anti-CSRF protection on requestsExamine the requests made when performing state-changing actions. Check if the requests include anti-CSRF tokens, and verify if Origin or Referer headers are validated server-side.Affected if State-changing requests lack anti-CSRF tokens and do not validate Origin/Referer headers
-
Check cookie security attributesInspect the session cookies returned by the application. Determine if they include the SameSite attribute and are configured to prevent cross-origin transmission.Affected if Session cookies do not have SameSite attribute set or allow cross-origin transmission
A user is affected if they are running PowerSCADA Anywhere or Citect Anywhere version 1.0 with the Secure Gateway web interface enabled and state-changing requests lack anti-CSRF protections such as tokens, Origin header validation, or SameSite cookie attributes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens for all state-changing operations, validate Origin/Referer headers on sensitive requests, and set SameSite cookie attributes to restrict cross-origin cookie transmission.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9963 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-9963 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data