dbcve.org
Vantara Pentaho Business Analytics ServerApplication · Hitachi

CVE-2022-43772

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-03
Fix available
A fix is available. Upgrade to 9.3.0.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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.4.0.0 and 9.3.0.1, including 8.3.x with the Big Data Plugin expose the username and password of clusters in clear text into system logs. 

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 versions before 9.4.0.0 and 9.3.0.1, as well as 8.3.x versions with the Big Data Plugin, expose Hadoop/big data cluster credentials (username and password) in clear text to system log files. This occurs during cluster authentication operations where credentials are logged unencrypted.

MitigationUpgrade Pentaho BA Server to version 9.4.0.0 or later. Additionally, rotate all exposed cluster credentials immediately and audit/secure or purge affected log files to prevent credential disclosure.

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.1

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
None

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

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 BA Server version
    Locate the Pentaho installation directory and check the version file or manifest. Common locations include version.info, manifest, or the server's about page in the Pentaho UI.
    Affected if The installed version is 9.3.0.1 or earlier, or is 9.3.x/9.4.x versions before 9.4.0.0, or is 8.3.x with the Big Data Plugin.
  2. Confirm Big Data Plugin is present
    Check the Pentaho installation for the Big Data Plugin (pentaho-big-data-plugin) directory or examine the plugins configuration. This is required for the vulnerability to be exploitable in 8.3.x versions.
    Affected if The Big Data Plugin is installed and enabled, particularly on 8.3.x versions.
  3. Examine Pentaho server log files for cleartext credentials
    Search Pentaho log files (typically pentaho.log, pentaho.log.1, or similar in the tomcat or pentaho/logs directory) for patterns matching Hadoop cluster credentials. Use grep or text search for strings containing username and password fields in authentication-related log entries.
    Affected if Log files contain cleartext username and password strings related to Hadoop or big data cluster authentication.
  4. Search for Hadoop cluster configuration files
    Locate Hadoop cluster configuration files in the Pentaho installation or data-integration directories. These files may reference connection credentials that could have been logged.
    Affected if Cluster configuration files exist and were used with affected Pentaho versions.

You are affected if running Pentaho BA Server version 9.3.0.1 or earlier, versions 9.3.x-9.4.0.0, or 8.3.x with the Big Data Plugin, AND cleartext credentials are found in log files.

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.1 or later
Fixed in 9.3.0.1
Interim mitigation

Upgrade Pentaho BA Server to version 9.4.0.0 or later. Additionally, rotate all exposed cluster credentials immediately and audit/secure or purge affected log files to prevent credential disclosure.

Recommended fix High confidence

9.3.0.1 or later (9.4.0.0+)

  1. 1. Back up your current Pentaho Business Analytics Server configuration and data.
  2. 2. Download Pentaho Business Analytics Server version 9.3.0.1 or later from the official Hitachi Vantara download portal.
  3. 3. Stop the Pentaho BA Server service.
  4. 4. Install the upgraded version following the standard upgrade procedure.
  5. 5. Restore your configuration and data from the backup.
  6. 6. Verify that cluster credentials are no longer being written to system logs.
  7. 7. Restart the Pentaho BA Server service.

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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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