dbcve.org
Vantara PentahoApplication · Hitachi

CVE-2021-45447

HIGH · 7.5 CVSS v3.1 Published 2022-11-02
Fix available
A fix is available. Upgrade to 8.3.0.25 / 9.2.0.2 or later.
See remediation →
84/100
Remediation priority · High
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.3.0.0, 9.2.0.2 and 8.3.0.25 with the Data Lineage feature enabled transmits database passwords in clear text.   The transmission of sensitive data in clear text allows unauthorized actors with access to the network to sniff and obtain sensitive information that can be later used to gain unauthorized access.

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

The Data Lineage feature in Hitachi Vantara Pentaho Business Analytics Server transmits database passwords in clear text across the network, allowing unauthenticated attackers with network access to intercept and capture sensitive credentials via sniffing.

MitigationUpgrade to Pentaho BA Server versions 9.3.0.0, 9.2.0.2, 8.3.0.25 or later. Alternatively, disable the Data Lineage feature if not needed, or implement TLS encryption for all network communications.

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 PentahoApplication
Affected:>= 8.3.0.0, < 8.3.0.25>= 9.2.0.0, < 9.2.0.2

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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-war JAR file or version manifest in the Pentaho server directory, or check the startup logs for the version string
    Affected if the installed version falls within 8.3.0.0 to 8.3.0.24 OR 9.2.0.0 to 9.2.0.1
  2. Determine if Data Lineage feature is in use
    Inspect the Pentaho configuration files (such as pentahoObjects.spring.xml or relevant datasource configuration) for Data Lineage module definitions or look for lineage-related data sources in the repository
    Affected if Data Lineage feature is configured and actively used to connect to databases
  3. Verify if database connections use TLS encryption
    Review the datasource connection settings in the Pentaho administration console or configuration files to check whether the 'useSSL' or 'encrypt' connection parameter is enabled
    Affected if TLS/SSL encryption is not enforced on the database connections used by Data Lineage
  4. Inspect network traffic from the Pentaho server
    Use a network capture tool on the interface where Pentaho traffic exits, observing outbound connections to database servers for plaintext credentials
    Affected if Clear text credentials are visible in network captures to database servers

You are affected if your Pentaho BA Server version is 8.3.0.0-8.3.0.24 or 9.2.0.0-9.2.0.1 AND the Data Lineage feature is enabled with database connections that are not TLS-encrypted.

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.25 / 9.2.0.2 or later
Fixed in 8.3.0.259.2.0.2
Interim mitigation

Upgrade to Pentaho BA Server versions 9.3.0.0, 9.2.0.2, 8.3.0.25 or later. Alternatively, disable the Data Lineage feature if not needed, or implement TLS encryption for all network communications.

Recommended fix High confidence

9.3.0.0 or later (minimum fixed versions: 8.3.0.25 for 8.x, 9.2.0.2 for 9.2.x)

  1. Identify the current Pentaho Business Analytics Server version in use
  2. Backup all existing Pentaho configurations, repositories, and databases
  3. Consult Pentaho release notes and upgrade documentation for the target version
  4. For versions 8.3.0.x: Upgrade to version 8.3.0.25
  5. For versions 9.2.0.x: Upgrade to version 9.2.0.2
  6. For versions 9.0.x-9.1.x: Upgrade to version 9.3.0.0 or later (recommended)
  7. After upgrade, verify that the Data Lineage feature functions correctly and database passwords are no longer transmitted in clear text
Caveat Review Pentaho release notes for version-specific breaking changes, particularly when upgrading across major version branches

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

Fix this in Vantara Pentaho Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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