dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-37361

CRITICAL · 9.9 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 →
100/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
The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid. (CWE-502)   Hitachi Vantara Pentaho Business Analytics Server versions before 10.2.0.0 and 9.3.0.9, including 8.3.x, deserialize untrusted JSON data without constraining the parser to approved classes and methods.   When developers place no restrictions on "gadget chains," or series of instances and method invocations that can self-execute during the deserialization process (i.e., before the object is returned to the caller), it is sometimes possible for attackers to leverage them to perform unauthorized actions.

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 deserializes untrusted JSON data without restricting which classes can be instantiated, enabling attackers to abuse gadget chains for arbitrary code execution or unauthorized actions. This insecure deserialization stems from the lack of an allowlist for approved classes during the deserialization process.

MitigationUpgrade to Pentaho Business Analytics Server version 10.2.0.0 or 9.3.0.9 or later. If immediate patching is not feasible, restrict network access to the server and implement additional input validation as compensating controls.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 Pentaho BA Server version
    Locate the version file in the Pentaho installation directory, typically version.xml or a manifest file in the server directory. You can also check the server startup logs or access the Pentaho Administration Console system info page if available.
    Affected if The installed version is earlier than 9.3.0.9 or 10.2.0.0, indicating it is a vulnerable release.
  2. Confirm network exposure of the server
    Determine if the Pentaho BA Server HTTP/HTTPS ports (default 8080 or 8443) are listening and accessible from network locations. Use netstat or similar tools to check listening ports and verify firewall rules.
    Affected if The server is directly accessible from network segments where untrusted users could send malicious JSON payloads.
  3. Inspect JSON deserialization configuration
    Examine Pentaho configuration files such as pentaho.xml, system properties, or any custom deserialization configuration for JSON processing settings. Look for class allowlist or whitelist settings that restrict which classes can be instantiated during deserialization.
    Affected if No class allowlist is configured for JSON deserialization, meaning the server accepts any serializable class.
  4. Review enabled Pentaho plugins or data sources
    Check which Pentaho plugins, data sources, or transformation steps are enabled that accept JSON input. The vulnerability applies when these components process untrusted JSON data.
    Affected if JSON-enabled features such as REST API calls, data input steps, or custom plugins are in use without additional validation layers.

The environment is affected if the installed Pentaho BA Server version is earlier than 9.3.0.9 or 10.2.0.0 and the server accepts JSON input from untrusted sources without class allowlist restrictions.

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 to Pentaho Business Analytics Server version 10.2.0.0 or 9.3.0.9 or later. If immediate patching is not feasible, restrict network access to the server and implement additional input validation as compensating controls.

Recommended fix Moderate confidence

10.2.0.0 or 9.3.0.9

  1. Identify the current Pentaho Business Analytics Server version in use
  2. Download the fixed version (9.3.0.9 or 10.2.0.0) from Hitachi Vantara support portal at support.pentaho.com
  3. Back up all existing Pentaho configurations, repositories, and databases
  4. Stop the Pentaho Server services
  5. Install the fixed version following the official upgrade documentation
  6. Start the Pentaho Server services
  7. Verify the installation was successful and the vulnerability is patched

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

Have this fixed 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 help mitigating

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-2024-37361 — 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-37361 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