# CVE-2019-7393: Cross-site scripting in CA Risk Authentication

> A remote attacker can exploit a UI redress vulnerability in the administrative interface to gain sensitive information.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-ccv6-2h77-2fvj

## What is CVE-2019-7393?

CVE-2019-7393 is a medium-severity cross-site scripting vulnerability in CA Risk Authentication, published on 28 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A UI redress vulnerability in the administrative user interface of CA Technologies CA Strong Authentication 9.0.x, 8.2.x, 8.1.x, 8.0.x, 7.1.x and CA Risk Authentication 9.0.x, 8.2.x, 8.1.x, 8.0.x, 3.1.x may allow a remote attacker to gain sensitive information in some cases.

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

## Which versions are affected by CVE-2019-7393?

It affects 2 products.


Products: Ca Risk Authentication, Ca Strong Authentication.

## How do I fix CVE-2019-7393?

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

## Is CVE-2019-7393 being exploited?

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

## Other vulnerabilities in CA Risk Authentication

- [CVE-2019-7394](https://insights.sbomify.com/CVE-2019-7394/): Privilege escalation in CA Risk Authentication (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7393 and fix it if it is affected.

What it is: CVE-2019-7393 is a medium-severity cross-site scripting vulnerability in CA Risk Authentication, published on 28 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7393 in the wild and no public exploit code.

Affected product: CA Risk Authentication. 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-2019-7393/ (Markdown: https://insights.sbomify.com/CVE-2019-7393/index.md)
```

## Sources

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

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