# CVE-2016-5997: Weak cryptography in n/a

> The web portal fails to enforce password quality rules, allowing attackers to easily compromise accounts via brute-force attacks.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/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:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r2mx-8c88-f5cf

## What is CVE-2016-5997?

CVE-2016-5997 is a medium-severity vulnerability in n/a, published on 26 Sep 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web portal in IBM Tealeaf Customer Experience before 8.7.1.8847 FP10, 8.8 before 8.8.0.9049 FP9, 9.0.0 and 9.0.1 before 9.0.1.1117 FP5, 9.0.1A before 9.0.1.5108_9.0.1A FP5, 9.0.2 before 9.0.2.1223 FP3, and 9.0.2A before 9.0.2.5224_9.0.2A FP3 does not apply password-quality rules to password changes, which makes it easier for remote attackers to obtain access via a brute-force attack.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2016-5997?

It affects 1 product.


Products: Ibm Tealeaf Customer Experience.

## How do I fix CVE-2016-5997?

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

## Is CVE-2016-5997 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-1204](https://insights.sbomify.com/CVE-2017-1204/): Hardcoded credentials in Tealeaf Customer Experience (critical 9.8)
- [CVE-2015-4988](https://insights.sbomify.com/CVE-2015-4988/): Path traversal in n/a (high 8.6)
- [CVE-2016-2983](https://insights.sbomify.com/CVE-2016-2983/): Information disclosure in Tealeaf Customer Experience (high 8.1)
- [CVE-2016-5996](https://insights.sbomify.com/CVE-2016-5996/): Weak cryptography in n/a (high 7.5)
- [CVE-2016-5977](https://insights.sbomify.com/CVE-2016-5977/): Open redirect in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5997 and fix it if it is affected.

What it is: CVE-2016-5997 is a medium-severity vulnerability in n/a, published on 26 Sep 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-5997 in the wild and no public exploit code.

Affected product: n/a. 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-2016-5997/ (Markdown: https://insights.sbomify.com/CVE-2016-5997/index.md)
```

## Sources

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

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