# CVE-2016-10701: Cross-site request forgery in n/a

> A Cross-Site Request Forgery vulnerability in Hitachi Vantara Pentaho BA Platform allows attackers to perform unauthorized actions on behalf of authenticated users.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Nov 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2fjx-98mq-mq2j

## What is CVE-2016-10701?

CVE-2016-10701 is a high-severity vulnerability in n/a, published on 28 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In Hitachi Vantara Pentaho BA Platform through 8.0, a CSRF issue exists in the Business Analytics application.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Hitachivantara Pentaho Business Analytics.

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

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

## Is CVE-2016-10701 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-3695](https://insights.sbomify.com/CVE-2022-3695/): Hitachi Vantara Pentaho Business Analytics Server - Improper Neutralization of Input During Web Page Generation (medium 6.5)
- [CVE-2022-43770](https://insights.sbomify.com/CVE-2022-43770/): Hitachi Vantara Pentaho Business Analytics Server - Incorrect Authorization (medium 5.4)
- [CVE-2023-2358](https://insights.sbomify.com/CVE-2023-2358/): Hitachi Vantara Pentaho Business Analytics Server – Password Stored in a Recoverable Format (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-10701 is a high-severity vulnerability in n/a, published on 28 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-10701 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-10701/ (Markdown: https://insights.sbomify.com/CVE-2016-10701/index.md)
```

## Sources

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

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