# CVE-2014-0436: Other in n/a

> Remote attackers can compromise data integrity in Oracle Hyperion BI+ Web Analysis via unspecified vectors.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 17 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9mjx-fxxr-3w7h

## What is CVE-2014-0436?

CVE-2014-0436 is a medium-severity vulnerability in n/a, published on 17 Jul 2014. It can be exploited over the network.

### Official description

Unspecified vulnerability in the Hyperion BI+ component in Oracle Hyperion 11.1.2.2 and 11.1.2.3 allows remote attackers to affect integrity via unknown vectors related to Web Analysis.

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

It affects 1 product.


Products: Oracle Hyperion.

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

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

## Is CVE-2014-0436 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-22062](https://insights.sbomify.com/CVE-2023-22062/): Information disclosure in Hyperion Financial Reporting (high 8.5)
- [CVE-2018-3142](https://insights.sbomify.com/CVE-2018-3142/): Information disclosure in Hyperion Essbase Administration Services (high 7.7)
- [CVE-2018-3140](https://insights.sbomify.com/CVE-2018-3140/): Cross-site scripting in Hyperion Essbase Administration Services (medium 6.1)
- [CVE-2014-2455](https://insights.sbomify.com/CVE-2014-2455/): Other in n/a (medium 6.0)
- [CVE-2018-3141](https://insights.sbomify.com/CVE-2018-3141/): Missing authorization in Hyperion Essbase Administration Services (medium 5.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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