# CVE-2017-9394: Cross-site scripting in CA Identity Governance

> Remote authenticated attackers can execute arbitrary scripts in the context of other users via stored XSS in CA Identity Governance.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-xfvr-53vp-crqh

## What is CVE-2017-9394?

CVE-2017-9394 is a medium-severity cross-site scripting vulnerability in CA Identity Governance, published on 14 Nov 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored cross-site scripting vulnerability in CA Identity Governance 12.6 allows remote authenticated attackers to display HTML or execute script in the context of another user.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Ca Identity Governance.

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

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

## Is CVE-2017-9394 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9394 is a medium-severity cross-site scripting vulnerability in CA Identity Governance, published on 14 Nov 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-9394 in the wild and no public exploit code.

Affected product: CA Identity Governance. 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-9394/ (Markdown: https://insights.sbomify.com/CVE-2017-9394/index.md)
```

## Sources

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

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