dbcve.org
Pentaho Business AnalyticsApplication · Hitachivantara

CVE-2022-43770

HIGH · 8.1 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 8.3.0.27 / 9.2.0.4 or later.
See remediation →
87/100
Remediation priority · High
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 versions before 9.3.0.0, 9.2.0.4 and 8.3.0.27 does not correctly perform an authorization check in the dashboard editor plugin API.   

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

Hitachi Vantara Pentaho Business Analytics Server contains an improper authorization vulnerability in the dashboard editor plugin API. The application fails to correctly perform authorization checks, potentially allowing authenticated users to access functionality or resources beyond their intended permissions.

MitigationApply the vendor-supplied patches by updating to version 9.3.0.0, 9.2.0.4, 8.3.0.27 or later. If patching is not immediately feasible, restrict access to the dashboard editor plugin API through network-level controls or authentication proxy.

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
Pentaho Business AnalyticsApplication
Affected:< 8.3.0.27>= 9.2.0.0, < 9.2.0.4

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Pentaho Business Analytics version
    Check the version.properties file in the Pentaho server directory (e.g., /pentaho/server/pentaho-marketplace/version.properties) or examine the startup logs for the version string
    Affected if The installed version is less than 8.3.0.27, or is 9.2.0.0 through 9.2.0.3
  2. Confirm the dashboard editor plugin is installed
    Inspect the pentaho-solutions/system directory for the dashboard-editor folder or check the Pentaho Marketplace plugin list via the admin console
    Affected if The dashboard editor plugin is present and enabled in the installation
  3. Verify the dashboard editor plugin API endpoint is accessible
    Attempt a GET request to the dashboard editor API endpoint (typically /pentaho/plugin/dashboard-editor/api/) or check the pentaho-solutions/system/dashboard-editor/config.xml for endpoint configuration
    Affected if The API endpoint responds without proper authorization failures (returns 200 OK instead of 401/403)
  4. Review plugin authorization configuration
    Examine the pentaho-solutions/system/dashboard-editor/security.properties or the main Pentaho security configuration files for role-based access control rules targeting the dashboard editor plugin
    Affected if No authorization constraints are defined for the dashboard editor API, or roles are missing/incomplete

The environment is affected if the installed Pentaho version falls within the vulnerable ranges (below 8.3.0.27 or 9.2.0.0-9.2.0.3) AND the dashboard editor plugin is installed with its API exposed without proper authorization controls.

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 8.3.0.27 / 9.2.0.4 or later
Fixed in 8.3.0.279.2.0.4
Interim mitigation

Apply the vendor-supplied patches by updating to version 9.3.0.0, 9.2.0.4, 8.3.0.27 or later. If patching is not immediately feasible, restrict access to the dashboard editor plugin API through network-level controls or authentication proxy.

Recommended fix High confidence

9.3.0.0 (or 9.2.0.4 for 9.2.x branch, 8.3.0.27 for 8.x branch)

  1. 1. Back up your current Pentaho Business Analytics Server installation, including the database and repository.
  2. 2. Stop the Pentaho Server service.
  3. 3. Download the appropriate fixed version based on your current major version: Pentaho 8.x users should download 8.3.0.27; Pentaho 9.2.x users should download 9.2.0.4; or upgrade to the latest stable version 9.3.0.0.
  4. 4. Install the fixed version following the standard Pentaho upgrade documentation.
  5. 5. Restore your configuration and repository data from the backup.
  6. 6. Verify the dashboard editor plugin API authorization is functioning correctly.
  7. 7. Restart the Pentaho Server service and test that the vulnerability is resolved.
Caveat Review Pentaho release notes for your target version to assess any breaking changes or required migration steps before upgrading

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

Fix this in Pentaho Business Analytics Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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