dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2024-37362

MEDIUM · 6.3 CVSS v3.1 Published 2025-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. (CWE-522)   Hitachi Vantara Pentaho Data Integration & Analytics versions before 10.2.0.0 and 9.3.0.8, including 8.3.x, discloses database passwords when saving connections to RedShift.   Products must not disclose sensitive information without cause. Disclosure of sensitive information can lead to further exploitation.

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 Data Integration & Analytics stores database credentials insecurely when saving RedShift connections, exposing plaintext or weakly protected passwords (CWE-522). Affected versions before 10.2.0.0 and 9.3.0.8, including 8.3.x, allow unauthorized retrieval of stored database passwords.

MitigationUpgrade Pentaho Data Integration to version 10.2.0.0 or 9.3.0.8 or later to obtain the security fix. Review and re-save existing RedShift connection configurations to ensure credentials are properly protected with the patched version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
Low

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

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 Data Integration version
    Check the product version in the installation directory, typically in a version file or about dialog. Common locations include 'version.properties' or check the manifest file in the Pentaho installation folder.
    Affected if The installed version is 8.3.x, or is before 9.3.0.8, or is before 10.2.0.0 (all vulnerable ranges)
  2. Locate RedShift connection configurations
    Search the Pentaho user workspace or repository for files containing RedShift connection settings. These are typically stored in XML files with names like '*.kdb' or connection XML files, often under the '.pentaho' or 'pentaho-solutions' directories in the user home folder.
    Affected if RedShift connection configuration files exist in the environment
  3. Inspect stored credentials for plaintext exposure
    Open the RedShift connection configuration files and examine the password field values. Look for passwords stored in plaintext or using weak encoding (base64 without encryption).
    Affected if Passwords appear as readable plaintext or use only basic encoding without proper encryption protection
  4. Verify credential protection mechanism
    Examine the connection configuration XML or properties files for the protection level of password fields. Check for attributes like 'protected' or 'encrypt' and verify the actual storage method.
    Affected if Password protection is set to 'none', 'plain', or uses a weak protection mechanism that allows retrieval in readable form

The environment is affected if Pentaho Data Integration version is 8.3.x, before 9.3.0.8, or before 10.2.0.0, AND RedShift connections with weakly protected credentials exist in the configuration.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Pentaho Data Integration to version 10.2.0.0 or 9.3.0.8 or later to obtain the security fix. Review and re-save existing RedShift connection configurations to ensure credentials are properly protected with the patched version.

Recommended fix High confidence

Pentaho Data Integration & Analytics 10.2.0.0 (or 9.3.0.8 as alternative)

  1. 1. Back up your existing Pentaho Data Integration & Analytics installation, including all repositories, jobs, and transformation files.
  2. 2. Download the fixed version: Pentaho Data Integration & Analytics 10.2.0.0 (recommended) or version 9.3.0.8 from Hitachi Vantara's official download portal.
  3. 3. Stop the Pentaho server and any running Carte slaves.
  4. 4. Install the new version following the official Pentaho installation guide for your platform.
  5. 5. Migrate your existing repositories, configuration files, and custom plugins to the new installation.
  6. 6. Verify that the RedShift connection configuration no longer exposes passwords in plain text by creating a new RedShift connection and inspecting the saved configuration file.
  7. 7. Restart the Pentaho server and validate that existing jobs and transformations function correctly.
Caveat Review release notes for any deprecated features or breaking changes between your current version and 10.2.0.0; test in non-production environment first

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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