dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Mar 2025.
Vantara Pentaho Business Analytics ServerApplication · Hitachi

CVE-2022-43769

HIGH · 7.2 CVSS v3.1 Published 2023-04-03
Fix available
A fix is available. Upgrade to 9.3.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Server-Side Template Injection (SSTI) vulnerability in Hitachi Vantara Pentaho BA Server. Certain web service endpoints accept property values containing Spring framework template syntax (e.g., #{...} SpEL expressions), which are interpreted/processed downstream during rendering, potentially enabling remote code execution.

MitigationUpgrade to Pentaho BA Server versions 9.4.0.1 or 9.3.0.2 and later. If immediate patching is not feasible, implement network-level access controls to restrict exposure of the affected web service endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vantara Pentaho Business Analytics ServerApplication
Affected:>= 8.3.0.0, < 9.3.0.2= 9.4.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pentaho BA Server installation
    Locate the Pentaho installation directory, typically under /pentaho or /opt/pentaho on Linux, or C:\pentaho on Windows. Look for the 'server' subdirectory containing pentaho.war or pentaho-style.war files.
    Affected if The Pentaho BA Server is not installed or this is a different component (e.g., Pentaho Data Integration only).
  2. Determine installed Pentaho BA Server version
    Check the version file in the installation directory. On Linux, look for version.txt or manifest.xml in the server/pentaho-server-managing directory. On Windows, check the installation folder properties or the 'system' directory for version information. Compare the found version against the affected ranges: 8.3.0.0 through 9.3.0.1, or exactly 9.4.0.0.
    Affected if The installed version falls within 8.3.0.0 <= version < 9.3.0.2 OR version equals exactly 9.4.0.0.
  3. Verify web services are network accessible
    Identify if the Pentaho BA Server web interface is exposed to the network. Check network configuration files or perform a port scan targeting typical Pentaho ports (8080, 8443). Look for the /pentaho/ endpoint accessible over HTTP/HTTPS.
    Affected if The Pentaho web services are reachable from the network without firewall restrictions or VLAN isolation.
  4. Confirm authentication status on vulnerable endpoints
    Review the Pentaho configuration files (particularly web.xml in the pentaho.war or pentaho-solutions/system directory) to determine if authentication is enforced on the web service endpoints. Check if anonymous access is permitted to the Spring-based property setting endpoints.
    Affected if The vulnerable web service endpoints allow unauthenticated access or rely on weak authentication mechanisms.

If the installed Pentaho BA Server version is 8.3.0.0 through 9.3.0.1 or exactly 9.4.0.0, AND the web services are network-accessible, the environment is likely affected by this SSTI vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.3.0.2 or later
Fixed in 9.3.0.2
Interim mitigation

Upgrade to Pentaho BA Server versions 9.4.0.1 or 9.3.0.2 and later. If immediate patching is not feasible, implement network-level access controls to restrict exposure of the affected web service endpoints.

Recommended fix High confidence

9.3.0.2 or 9.4.0.1

  1. Backup the Pentaho Business Analytics Server configuration, repository, and databases
  2. Download Pentaho Business Analytics Server version 9.3.0.2 or 9.4.0.1 from the official Hitachi Vantara support portal
  3. Stop the Pentaho server services
  4. Install the upgraded version following the standard upgrade documentation
  5. Restore the configuration and repository from the backup
  6. Start the Pentaho server services
  7. Verify the web services functionality and confirm the vulnerability is resolved
Caveat Review release notes for any configuration or feature changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vantara Pentaho Business Analytics Server Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43769 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43769 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data