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-43939

CRITICAL · 9.8 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 No privileges 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 versions before 9.4.0.1 and 9.3.0.2, including 8.3.x contain security restrictions using non-canonical URLs which can be circumvented.

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 · moderate confidence

Hitachi Vantara Pentaho Business Analytics Server contains a security bypass vulnerability where security restrictions enforcing canonical URL paths can be circumvented through non-canonical URL requests. This allows attackers to potentially bypass access controls by using specially crafted URLs that deviate from canonical path formats.

MitigationUpgrade Pentaho Business Analytics Server to version 9.4.0.1, 9.3.0.2, or later. All affected versions before these release points (including 8.3.x) are vulnerable.

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:< 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate Pentaho Business Analytics Server version
    Check the server's about page, version manifest, or startup logs for the installed Pentaho version number. Common locations include the /pentaho/about page, version.properties file in the installation directory, or server startup output.
    Affected if The version cannot be confirmed or is not visible through standard methods.
  2. Compare installed version against affected range
    Identify the exact version number from step 1 and compare it against the affected ranges: versions below 9.3.0.2, or exactly version 9.4.0.0.
    Affected if Installed version is less than 9.3.0.2 OR installed version equals exactly 9.4.0.0.
  3. Confirm version is NOT in safe range
    Verify the installed version is not 9.3.0.2 or 9.4.0.1 and later. These versions contain the security fix.
    Affected if The version cannot be confirmed as 9.3.0.2 or 9.4.0.1 or later.
  4. Check if web interface is accessible
    Confirm the Pentaho web interface is network-accessible. This vulnerability is exploitable through HTTP requests to the web application.
    Affected if The Pentaho web interface is exposed and the version is in the affected range.

You are affected if your Pentaho Business Analytics Server version is below 9.3.0.2 or exactly 9.4.0.0, and the web interface is accessible.

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 Pentaho Business Analytics Server to version 9.4.0.1, 9.3.0.2, or later. All affected versions before these release points (including 8.3.x) are vulnerable.

Recommended fix Moderate confidence

Upgrade to Pentaho BA Server 9.3.0.2 or 9.4.0.1 (or later supported release)

  1. 1. Back up your Pentaho BA Server configuration, repository, and database before proceeding with the upgrade.
  2. 2. Download the fixed version of Pentaho Business Analytics Server (9.3.0.2 or 9.4.0.1) from the official Hitachi Vantara support portal.
  3. 3. Stop the Pentaho BA Server service.
  4. 4. If upgrading from 8.3.x, ensure your environment meets the system requirements for version 9.x.
  5. 5. Install the new version of Pentaho BA Server, preserving your existing configuration and repository data.
  6. 6. Start the Pentaho BA Server service.
  7. 7. Verify that the server is running correctly and test that security restrictions are functioning as expected.
  8. 8. Review Pentaho documentation for any post-upgrade configuration adjustments needed.
Caveat Upgrading from 8.3.x to 9.x may require system requirement changes and configuration adjustments; review Hitachi Vantara upgrade documentation

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43939 — 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-43939 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