dbcve.org
Vantara Pentaho Business Analytics ServerApplication · Hitachi

CVE-2022-43773

HIGH · 8.8 CVSS v3.1 Published 2023-04-03
Fix available
A fix is available. Upgrade to 9.3.0.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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 is installed with a sample HSQLDB data source configured with stored procedures enabled. 

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 ships with a sample HSQLDB database that has stored procedures enabled, which can be exploited to achieve remote code execution or unauthorized file system access due to HSQLDB's capability to execute Java code through stored procedures.

MitigationUpdate to version 9.4.0.1 or 9.3.0.2, or remove/disable the sample HSQLDB data source and its associated stored procedures functionality.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Pentaho Business Analytics Server version
    Locate the version manifest or about dialog in the Pentaho installation (commonly in version.xml, about.html, or the server startup logs) and record the full version number
    Affected if The version is >= 8.3.0.0 and < 9.3.0.2, or equals 9.4.0.0 exactly
  2. Determine if sample HSQLDB data source is present
    Search for HSQLDB-related configuration files or data source definitions in the Pentaho configuration directories (look for files containing 'hsqldb' or 'sampledata' in the data source or solution configuration areas)
    Affected if A sample HSQLDB database or data source configuration file exists and is enabled in the Pentaho environment
  3. Verify if HSQLDB database is accessible or in use
    Check the Pentaho data source configuration for any active connection to an HSQLDB database, or examine whether HSQLDB-related JAR files are present in the Pentaho lib directory
    Affected if HSQLDB is configured as an active data source in Pentaho
  4. Confirm stored procedures functionality is enabled for HSQLDB
    Examine the HSQLDB database configuration or the Pentaho data source settings to determine if stored procedure execution is permitted (look for settings that enable CALL support or custom stored procedures in the database connection)
    Affected if Stored procedures or custom SQL execution is allowed on the HSQLDB data source

A user is affected if their Pentaho Business Analytics Server version falls within the vulnerable range AND the sample HSQLDB data source with stored procedures enabled is present and active in their environment.

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

Update to version 9.4.0.1 or 9.3.0.2, or remove/disable the sample HSQLDB data source and its associated stored procedures functionality.

Recommended fix High confidence

Upgrade to Pentaho Business Analytics Server 9.4.0.1 or 9.3.0.2 (whichever aligns with your release branch)

  1. 1. Back up all existing Pentaho data, repositories, and configuration files before upgrading.
  2. 2. Download the fixed version from Hitachi Vantara support portal: either version 9.3.0.2 or 9.4.0.1 (depending on your target branch).
  3. 3. Stop the Pentaho Business Analytics Server service.
  4. 4. Install or upgrade to the selected fixed version (9.3.0.2 or 9.4.0.1).
  5. 5. After upgrade, verify that the sample HSQLDB data source has been removed or reconfigured with stored procedures disabled.
  6. 6. Restart the Pentaho Business Analytics Server service.
  7. 7. Validate that the application functions correctly with the new version.
Caveat Review release notes for any deprecated features or configuration changes between your current version and the target fixed version

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

Fix this in Vantara Pentaho Business Analytics Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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