# CVE-2023-3517: Hitachi Vantara Pentaho Data Integration & Analytics - Improper Control of Resource Identifiers ('Resource Injection')

> Attackers can manipulate JNDI identifiers in XActions to control system-level data sources in Pentaho Data Integration.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5w65-7gfr-vxjf

## What is CVE-2023-3517?

CVE-2023-3517 is a high-severity vulnerability in Hitachi Vantara Pentaho Data Integration & Analytics, published on 12 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hitachi Vantara Pentaho Data Integration & Analytics versions before 9.5.0.1 and 9.3.0.5, including 
8.3.x does not restrict JNDI identifiers during the creation of XActions, allowing control of system level data sources.

Weakness: CWE-99 (Improper Control of Resource Identifiers)

## Which versions are affected by CVE-2023-3517?

It affects 1 product.


Products: Hitachi Pentaho Data Integration and Analytics.

## How do I fix CVE-2023-3517?

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

## Is CVE-2023-3517 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3517 and fix it if it is affected.

What it is: CVE-2023-3517 is a high-severity vulnerability in Hitachi Vantara Pentaho Data Integration & Analytics, published on 12 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3517 in the wild and no public exploit code.

Affected product: Hitachi Vantara Pentaho Data Integration & Analytics. 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-2023-3517/ (Markdown: https://insights.sbomify.com/CVE-2023-3517/index.md)
```

## Sources

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

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