dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-5705

HIGH · 8.8 CVSS v3.1 Published 2025-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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 product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. (CWE-863)     Hitachi Vantara Pentaho Business Analytics Server versions before 10.2.0.0 and 9.3.0.9, including 8.3.x, have modules enabled by default that allow execution of system level processes.   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 · high confidence

Hitachi Vantara Pentaho Business Analytics Server versions before 10.2.0.0 and 9.3.0.9 (including 8.3.x) contain default modules that enable execution of system-level processes. The application incorrectly applies or bypasses authorization checks, allowing authenticated users to perform actions and access resources beyond their intended permissions.

MitigationUpgrade Pentaho Business Analytics Server to version 10.2.0.0 or 9.3.0.9 or later to patch the authorization bypass vulnerability. Review and disable any unnecessary default modules that expose system-level process execution capabilities.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 installed Pentaho Business Analytics Server version
    Check the version information in the Pentaho server installation, typically found in version manifest files or the pentaho.war/WEB-INF/web.xml version string, or by accessing the /api/system/status endpoint if available
    Affected if The installed version is 8.3.x, 9.x before 9.3.0.9, or 10.x before 10.2.0.0
  2. Confirm the server is running with default modules enabled
    Inspect the pentaho-solution/system directory for default module configurations that expose system-level process execution capabilities
    Affected if Default modules that enable system-level process execution are present and enabled in the configuration
  3. Verify authorization configuration for the affected modules
    Review the application-level authorization settings and pentaho-spring-beans.xml or similar security configuration files to determine if authorization checks are properly applied to default modules
    Affected if Authorization checks are incorrectly applied, bypassed, or missing for modules that expose system-level process execution
  4. Check for unauthorized access by lower-privileged users
    Review audit logs or access logs for authenticated users performing actions or accessing resources outside their assigned role permissions, particularly system-level operations
    Affected if Authenticated users with limited roles can access resources or execute system-level processes beyond their intended permissions

You are affected if your Pentaho Business Analytics Server version is 8.3.x, 9.x before 9.3.0.9, or 10.x before 10.2.0.0 AND default modules with system-level process execution capabilities are enabled without proper authorization controls.

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 Business Analytics Server to version 10.2.0.0 or 9.3.0.9 or later to patch the authorization bypass vulnerability. Review and disable any unnecessary default modules that expose system-level process execution capabilities.

Recommended fix High confidence

Upgrade to Pentaho Business Analytics Server 10.2.0.0 or later, or 9.3.0.9 or later

  1. Identify the current Pentaho Business Analytics Server version in use
  2. Determine which upgrade path is appropriate (10.2.x branch or 9.3.x branch) based on compatibility requirements
  3. Backup the existing Pentaho installation, including configuration files and databases
  4. Test the upgrade in a non-production environment to verify functionality
  5. Apply the upgrade to production environment by installing version 10.2.0.0 or later, or 9.3.0.9 or later
  6. Verify that the authorization controls are functioning correctly post-upgrade
  7. Review user roles and permissions to ensure access controls are properly configured
Caveat Review Pentaho release notes for breaking changes between current version and target version, as major version upgrades may introduce compatibility changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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