# CVE-2015-7449: Weak cryptography in n/a

> Local users can obtain sensitive information due to weak encryption in IBM Rational Collaborative Lifecycle Management products.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fhgc-mxcj-wgh5

## What is CVE-2015-7449?

CVE-2015-7449 is a low-severity vulnerability in Ibm Rational Collaborative Lifecycle Management, published on 20 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Rational Collaborative Lifecycle Management (CLM) 4.0.x before 4.0.7 iFix10, 5.0.x before 5.0.2 iFix15, 6.0.x before 6.0.1 iFix5, and 6.0.2 before iFix2; Rational Quality Manager (RQM) 4.0.x before 4.0.7 iFix10, 5.0.x before 5.0.2 iFix15, 6.0.x before 6.0.1 iFix5, and 6.0.2 before iFix2; Rational Team Concert (RTC) 4.0.x before 4.0.7 iFix10, 5.0.x before 5.0.2 iFix15, 6.0.x before 6.0.1 iFix5, and 6.0.2 before iFix2; Rational Requirements Composer (RRC) 4.0.x before 4.0.7 iFix10; Rational DOORS Next Generation (RDNG) 4.0.x before 4.0.7 iFix10, 5.0.x before 5.0.2 iFix15, 6.0.x before 6.0.1 iFix5, and 6.0.2 before iFix2; Rational Engineering Lifecycle Manager (RELM) 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7 before iFix1, 5.0.x before 5.0.2 iFix1, and 6.0.x before 6.0.2; Rational Rhapsody Design Manager (Rhapsody DM) 4.0.x before 4.0.7 iFix10, 5.0.x before 5.0.2 iFix15, 6.0.x before 6.0.1 iFix5, and 6.0.2 before iFix2; Rational Software Architect Design Manager (RSA DM) 4.0.x before 4.0.7 iFix10, 5.0.x before 5.0.2 iFix15, 6.0.x before 6.0.1 iFix5, and 6.0.2 before iFix2 allow local users to obtain sensitive information by leveraging weak encryption. IBM X-Force ID: 108221.

Weakness: CWE-326 (Inadequate Encryption Strength), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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-7449?

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

## Is CVE-2015-7449 being exploited?

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

What it is: CVE-2015-7449 is a low-severity vulnerability in Ibm Rational Collaborative Lifecycle Management, published on 20 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7449 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-7449/ (Markdown: https://insights.sbomify.com/CVE-2015-7449/index.md)
```

## Sources

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

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