# CVE-2015-1928: Other in n/a

> Remote authenticated users can conduct clickjacking attacks via a crafted website in IBM Rational Collaborative Lifecycle Management products.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/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:** 2 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3ggw-j4v8-rwmq

## What is CVE-2015-1928?

CVE-2015-1928 is a medium-severity vulnerability in Ibm Rational Collaborative Lifecycle Management, published on 2 Jan 2016. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Jazz Team Server in Jazz Foundation in IBM Rational Collaborative Lifecycle Management (CLM) 3.x and 4.x before 4.0.7 IF9, 5.x before 5.0.2 IF11, and 6.x before 6.0.0 IF4; Rational Quality Manager (RQM) 3.x before 3.0.1.6 IF7, 4.x before 4.0.7 IF9, 5.x before 5.0.2 IF11, and 6.0 before 6.0.0 IF4; Rational Team Concert (RTC) 3.x before 3.0.1.6 IF7, 4.x before 4.0.7 IF9, 5.x before 5.0.2 IF11, and 6.0 before 6.0.0 IF4; Rational Requirements Composer (RRC) 3.x before 3.0.1.6 IF7 and 4.x before 4.0.7 IF9; Rational DOORS Next Generation (RDNG) 4.x before 4.0.7 IF9, 5.x before 5.0.2 IF11, and 6.0 before 6.0.0 IF4; Rational Engineering Lifecycle Manager (RELM) 4.0.3 through 4.0.7, 5.0 through 5.0.2, and 6.0.0; Rational Rhapsody Design Manager (DM) 4.0 through 4.0.7, 5.0 through 5.0.2, and 6.0.0; and Rational Software Architect Design Manager (DM) 4.0 through 4.0.7, 5.0 through 5.0.2, and 6.0.0 allows remote authenticated users to conduct clickjacking attacks via a crafted web site.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-1928?

It affects 8 products.


Products: Ibm Rational Collaborative Lifecycle Management, Ibm Rational Doors Next Generation, Ibm Rational Engineering Lifecycle Manager, Ibm Rational Quality Manager, Ibm Rational Requirements Composer, Ibm Rational Rhapsody Design Manager, Ibm Rational Software Architect Design Manager, Ibm Rational Team Concert.

## How do I fix CVE-2015-1928?

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

## Is CVE-2015-1928 being exploited?

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

## Other vulnerabilities in Ibm Rational Collaborative Lifecycle Management

- [CVE-2014-0862](https://insights.sbomify.com/CVE-2014-0862/): Code injection in n/a (critical 10.0)
- [CVE-2017-1701](https://insights.sbomify.com/CVE-2017-1701/): Weak cryptography in Rational Team Concert (high 8.8)
- [CVE-2016-0326](https://insights.sbomify.com/CVE-2016-0326/): Command injection in n/a (high 8.8)
- [CVE-2016-9707](https://insights.sbomify.com/CVE-2016-9707/): XML external entity in Rational Collaborative Lifecycle Management (high 8.1)
- [CVE-2015-7440](https://insights.sbomify.com/CVE-2015-7440/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1928 and fix it if it is affected.

What it is: CVE-2015-1928 is a medium-severity vulnerability in Ibm Rational Collaborative Lifecycle Management, published on 2 Jan 2016. 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-2015-1928 in the wild and no public exploit code.

Affected product: Ibm Rational Collaborative Lifecycle Management. 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-2015-1928/ (Markdown: https://insights.sbomify.com/CVE-2015-1928/index.md)
```

## Sources

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

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