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

> Remote attackers can perform port scanning via timing differences in SAP BusinessObjects Explorer, exposing internal network topology.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5qp3-hxwx-86vp

## What is CVE-2014-8315?

CVE-2014-8315 is a medium-severity vulnerability in n/a, published on 16 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

polestar_xml.jsp in SAP BusinessObjects Explorer 14.0.5 build 882 replies with different timing depending on if a connection can be made, which allows remote attackers to conduct port scanning attacks via a host name and port in the cms parameter.

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

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

It affects 1 product.


Products: Sap Businessobjects Explorer.

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

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

## Is CVE-2014-8315 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-8316](https://insights.sbomify.com/CVE-2014-8316/): XML external entity in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8315 is a medium-severity vulnerability in n/a, published on 16 Oct 2014. 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-2014-8315 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-8315/ (Markdown: https://insights.sbomify.com/CVE-2014-8315/index.md)
```

## Sources

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

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