CVE-2024-37363
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 · uneditedThe product does not perform an authorization check when an actor attempts to access a resource or perform an action. (CWE-862) Hitachi Vantara Pentaho Business Analytics Server versions before 10.2.0.0 and 9.3.0.8, including 8.3.x, do not correctly perform an authorization check in the data source management service. When access control checks are incorrectly applied, users can access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures and denial of service.
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 confidenceHitachi Vantara Pentaho Business Analytics Server versions before 10.2.0.0 and 9.3.0.8 (including 8.3.x) contain an authorization bypass vulnerability in the data source management service. The product fails to correctly perform authorization checks (CWE-862), allowing authenticated users to access data or perform actions outside their intended permissions, potentially leading to information disclosure or denial of service.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Pentaho Business Analytics Server versionLocate the version information in the Pentaho installation directory (such as version files, manifest, or about page in the server console). Alternatively, check the startup logs or the Pentaho Administration Console for the exact version number.Affected if The installed version is 9.3.0.7 or earlier, 9.4.0.0 through 10.1.x, or any 8.3.x version (i.e., any version below 9.3.0.8 or 10.2.0.0)
-
Confirm the data source management service is accessibleVerify that the Pentaho data source management service (typically accessible via /pentaho/data-source management endpoints or the Data Source dialog in the user interface) is enabled and exposed to users.Affected if The data source management interface is available to authenticated users in the environment
-
Review user role assignments for data source permissionsExamine the user and role configuration in Pentaho to determine which authenticated users have access to the data source management functionality, and verify if the authorization boundaries align with intended permissions.Affected if Users with standard authenticated access can reach data source management endpoints beyond their designated scope
-
Check for unauthorized data source access attempts in logsReview Pentaho server logs (in the installation logs directory) for anomalous data source management operations that may indicate exploitation of the authorization bypass.Affected if Logs show data source access or modifications by users outside their expected permission scope
A user is affected if their Pentaho Business Analytics Server version is below 9.3.0.8 or 10.2.0.0 AND the data source management service is accessible to authenticated users in the environment.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Pentaho Business Analytics Server to version 10.2.0.0, 9.3.0.8, or later to implement proper authorization checks in the data source management service.
Upgrade to 10.2.0.0 (if on 10.x branch) or 9.3.0.8 (if on 9.x branch); 8.3.x users should migrate to 9.3.0.8 or later
- 1. Identify your current Pentaho Business Analytics Server version by checking the server console or documentation.
- 2. If running version 10.x: Plan upgrade to version 10.2.0.0 or later.
- 3. If running version 9.x: Plan upgrade to version 9.3.0.8 or later.
- 4. If running version 8.3.x: Plan upgrade to version 9.3.0.8 or later (9.x is the recommended migration path for legacy 8.x installations).
- 5. Before upgrading in production, test the new version in a staging environment to verify compatibility with your existing data sources and workflows.
- 6. Perform a full backup of your Pentaho configuration, repositories, and databases before upgrading.
- 7. Apply the upgrade following Hitachi Vantara's official upgrade documentation for your version path.
- 8. After upgrading, verify that the data source management service authorization controls are functioning correctly.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-37363 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37363 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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