# CVE-2018-1255: Reflected Cross-Site Scripting Vulnerability

> Remote attackers can execute arbitrary scripts in victim browsers via reflected XSS in RSA Identity Lifecycle and Governance.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 13 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9qvx-98rw-g873

## What is CVE-2018-1255?

CVE-2018-1255 is a medium-severity cross-site scripting vulnerability in RSA Identity Governance and Lifecycle, published on 13 Jul 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

RSA Identity Lifecycle and Governance versions 7.0.1, 7.0.2 and 7.1.0 contains a reflected cross-site scripting vulnerability. A remote unauthenticated attacker could potentially exploit this vulnerability by tricking a victim application user to supply malicious HTML or JavaScript code to a vulnerable web application, which is then reflected back to the victim and executed by the web browser.

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

## Which versions are affected by CVE-2018-1255?

It affects 1 product.


Products: Emc Rsa Identity Governance and Lifecycle.

## How do I fix CVE-2018-1255?

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

## Is CVE-2018-1255 being exploited?

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

## Other vulnerabilities in RSA Identity Governance and Lifecycle

- [CVE-2018-1245](https://insights.sbomify.com/CVE-2018-1245/): Authorization ByPass Vulnerability (critical 9.0)
- [CVE-2018-1182](https://insights.sbomify.com/CVE-2018-1182/): Privilege escalation in EMC RSA Identity Governance and Lifecycle versions 7.0.1, 7.0.2, all patch levels (hardware appliance and software bundle deployments only); RSA Via Lifecycle and Governance version 7.0, all patch levels (hardware appliance and software bundle deployments only); RSA Identity Management & Governance (RSA IMG) versions 6.9.0, 6.9.1, all patch levels (hardware appliance and software bundle deployments only) (high 7.8)
- [CVE-2018-11049](https://insights.sbomify.com/CVE-2018-11049/): RSA Identity Governance and Lifecycle Uncontrolled Search Path Vulnerability (high 7.3)
- [CVE-2017-8004](https://insights.sbomify.com/CVE-2017-8004/): File upload in RSA Identity Governance and Lifecycle, RSA Via Lifecycle and Governance, RSA Identity Management and Governance (RSA IMG) (high 7.2)
- [CVE-2017-5003](https://insights.sbomify.com/CVE-2017-5003/): Cross-site scripting in RSA Identity Governance and Lifecycle versions 7.0.1, 7.0.2, all patch levels, RSA Via Lifecycle and Governance version 7.0, all patch levels, RSA Identity Management and Governance (RSA IMG) versions 6.9.1, all patch levels (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1255 and fix it if it is affected.

What it is: CVE-2018-1255 is a medium-severity cross-site scripting vulnerability in RSA Identity Governance and Lifecycle, published on 13 Jul 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-2018-1255 in the wild and no public exploit code.

Affected product: RSA Identity Governance and Lifecycle. 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-2018-1255/ (Markdown: https://insights.sbomify.com/CVE-2018-1255/index.md)
```

## Sources

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

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