# CVE-2018-1694: Information disclosure in Rational Collaborative Lifecycle Management

> Remote attackers can obtain sensitive information via man-in-the-middle attacks due to missing HTTP Strict Transport Security headers in IBM Jazz applications.

- **Severity:** Medium 5.9 (`CVSS:3.0/A:N/AC:H/AV:N/C:H/I:N/PR:N/S:U/UI:N/E:U/RC:C/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Nov 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4rww-qqx8-7693

## What is CVE-2018-1694?

CVE-2018-1694 is a medium-severity vulnerability in Ibm Rational Collaborative Lifecycle Management, published on 6 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Jazz applications (IBM Rational Collaborative Lifecycle Management 5.0 through 5.02 and 6.0 through 6.0.6, IBM Rational DOORS Next Generation 5.0 through 5.02 and 6.0 through 6.0.6, IBM Rational Engineering Lifecycle Manager 5.0 through 5.02 and 6.0 through 6.0.6, IBM Rational Quality Manager 5.0 through 5.02 and 6.0 through 6.0.6, IBM Rational Rhapsody Design Manager 5.0 through 5.02 and 6.0 through 6.0.6, IBM Rational Software Architect Design Manager 5.0 through 5.02 and 6.0 through 6.0.1, IBM Rational Team Concert 5.0 through 5.02 and 6.0 through 6.0.6) could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques. IBM X-Force ID: 145609.

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

It affects 7 products.


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

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

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

## Is CVE-2018-1694 being exploited?

There is no known exploitation of CVE-2018-1694 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-2018-1694 and fix it if it is affected.

What it is: CVE-2018-1694 is a medium-severity vulnerability in Ibm Rational Collaborative Lifecycle Management, published on 6 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1694 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-2018-1694/ (Markdown: https://insights.sbomify.com/CVE-2018-1694/index.md)
```

## Sources

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

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