# CVE-2016-0382: Information disclosure in Tealeaf Customer Experience

> Attackers can access exposed operational state data from the IBM Tealeaf Customer Experience portal via network infrastructure components.

- **Severity:** Medium 4.0 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q7vr-fg9g-8q52

## What is CVE-2016-0382?

CVE-2016-0382 is a medium-severity vulnerability in IBM Corporation Tealeaf Customer Experience, published on 3 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The IBM Tealeaf Consumer Experience 8.7, 8.8, and 9.0 portal exposes some of its operational state in a form that may be accidentally captured and exposed by network infrastructure components such as IIS. IBM X-Force ID: 112356.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Ibm Tealeaf Consumer Experience.

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

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

## Is CVE-2016-0382 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-0382 is a medium-severity vulnerability in IBM Corporation Tealeaf Customer Experience, published on 3 May 2017. 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-2016-0382 in the wild and no public exploit code.

Affected product: IBM Corporation Tealeaf Customer Experience. 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-0382/ (Markdown: https://insights.sbomify.com/CVE-2016-0382/index.md)
```

## Sources

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

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