# CVE-2014-8665: Information disclosure in n/a

> Remote attackers can obtain sensitive information by reading unspecified files in the SAP Business Intelligence Development Workbench.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Nov 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c3x9-q2xr-p67f

## What is CVE-2014-8665?

CVE-2014-8665 is a medium-severity vulnerability in n/a, published on 6 Nov 2014. It can be exploited over the network, with no action from the victim.

### Official description

The SAP Business Intelligence Development Workbench allows remote attackers to obtain sensitive information by reading unspecified files.

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

## Which versions are affected by CVE-2014-8665?

It affects 1 product.


Products: Sap Business Intelligence Development Workbench.

## How do I fix CVE-2014-8665?

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

## Is CVE-2014-8665 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-8666](https://insights.sbomify.com/CVE-2014-8666/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8665 and fix it if it is affected.

What it is: CVE-2014-8665 is a medium-severity vulnerability in n/a, published on 6 Nov 2014. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8665 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-2014-8665/ (Markdown: https://insights.sbomify.com/CVE-2014-8665/index.md)
```

## Sources

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

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