# CVE-2022-43769: Hitachi Vantara Pentaho BA Server Special Element Injection

> Attackers can inject Spring templates via web services to execute arbitrary code on Hitachi Vantara Pentaho Business Analytics Server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Mar 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-wc6x-gmp9-8p34

## What is CVE-2022-43769?

CVE-2022-43769 is a high-severity code injection vulnerability in Hitachi Vantara Pentaho Business Analytics Server, published on 3 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hitachi Vantara Pentaho Business Analytics Server prior to versions 9.4.0.1 and 9.3.0.2, including 8.3.x allow certain web services to set property values which contain Spring templates that are interpreted downstream.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2022-43769?

It affects 1 product.


Products: Hitachi Vantara Pentaho Business Analytics Server.

## How do I fix CVE-2022-43769?

No fix has been published for CVE-2022-43769 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Mar 2025.

## Is CVE-2022-43769 being exploited?

Yes. Attackers have exploited CVE-2022-43769 in the wild since at least 3 Mar 2025.

Public exploit code:

- Pentaho Business Server Auth Bypass and Server Side Template Injection RCE (metasploit)
- Pentaho BA Server EE 9.3.0.0-428 - Remote Code Execution (RCE) (Unauthenticated) (exploitdb)
- Hitachi Pentaho Business Analytics Server - Remote Code Execution (nuclei): http/cves/2022/CVE-2022-43769.yaml

## Other vulnerabilities in Hitachi Vantara Pentaho Business Analytics Server

- [CVE-2022-43939](https://insights.sbomify.com/CVE-2022-43939/): Hitachi Vantara Pentaho BA Server Authorization Bypass (high 8.6, exploited in the wild)
- [CVE-2022-43773](https://insights.sbomify.com/CVE-2022-43773/): Hitachi Vantara Pentaho Business Analytics Server - Incorrect Permission Assignment for Critical Resource (high 8.8)
- [CVE-2022-43938](https://insights.sbomify.com/CVE-2022-43938/): Code injection in Pentaho Business Analytics Server (high 8.8)
- [CVE-2022-43940](https://insights.sbomify.com/CVE-2022-43940/): Hitachi Vantara Pentaho Business Analytics Server - Incorrect Authorization (high 8.8)
- [CVE-2022-43941](https://insights.sbomify.com/CVE-2022-43941/): Hitachi Vantara Pentaho Business Analytics Server - Improper Restriction of XML External Entity Reference (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43769 and fix it if it is affected.

What it is: CVE-2022-43769 is a high-severity code injection vulnerability in Hitachi Vantara Pentaho Business Analytics Server, published on 3 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-43769 in the wild since at least 3 Mar 2025.

Affected product: Hitachi Vantara Pentaho Business Analytics Server. 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-2022-43769/ (Markdown: https://insights.sbomify.com/CVE-2022-43769/index.md)
```

## Sources

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

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