dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-0758

MEDIUM · 6.1 CVSS v3.1 Published 2025-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
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
Overview  The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. (CWE-732)  Description  Hitachi Vantara Pentaho Business Analytics Server prior to versions 10.2.0.2, including 9.3.x and 8.3.x, is installed with Karaf JMX beans enabled and accessible by default.  Impact  When the vulnerability is leveraged, a user with local execution privileges can access functionality exposed by Karaf beans contained in the product.

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 prior to version 10.2.0.2 ships with Karaf JMX beans enabled and accessible by default, allowing users with local execution privileges to access sensitive functionality exposed through these management beans. This represents an incorrect permission assignment (CWE-732) on a security-critical resource.

MitigationDisable or properly secure the Karaf JMX beans by restricting access and/or requiring authentication, upgrading to version 10.2.0.2 or later, or implementing network-level access controls to limit exposure.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/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 Pentaho installation directory and check for version information in version.xml, about.html, or the pentahoBI platform configuration files. Alternatively, check the startup logs or use the version command if available.
    Affected if The installed version is prior to 10.2.0.2 (for example, 10.1.0.x, 9.x, or earlier)
  2. Locate Karaf JMX configuration
    Navigate to the Pentaho installation directory and look for the Karaf etc folder (commonly at data/karaf/etc or pentaho-solutions/system/karaf/etc). Identify JMX-related configuration files such as jmx.acl.cfg, org.apache.karaf.management.cfg, or jmx-remoting.access.
    Affected if Karaf JMX configuration files exist and are present in the default installation
  3. Verify JMX bean accessibility
    Open the jmx.acl.cfg or equivalent JMX access control configuration file and check if the beans are configured with open or unauthenticated access. Look for entries like role-based access controls set to admin, monitor, or viewer with no password protection.
    Affected if JMX beans are accessible without authentication or with default permissive settings
  4. Check file permissions on Karaf config
    Review file system permissions on the Karaf etc configuration directory and JMX config files. Verify which system users have read or write access to these files.
    Affected if Permissions allow local users with basic execution privileges to read or modify JMX configuration

You are affected if your Pentaho BA Server version is prior to 10.2.0.2 and the Karaf JMX beans are enabled with default accessible settings.

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

Disable or properly secure the Karaf JMX beans by restricting access and/or requiring authentication, upgrading to version 10.2.0.2 or later, or implementing network-level access controls to limit exposure.

Recommended fix High confidence

Pentaho Business Analytics Server 10.2.0.2 or later

  1. Identify the current Pentaho Business Analytics Server version running in your environment
  2. Create a complete backup of the current Pentaho installation including configuration files and data directories
  3. Download Pentaho Business Analytics Server version 10.2.0.2 or a later stable release from the official Hitachi Vantara Pentaho support portal
  4. Stop the Pentaho server and any related services
  5. Perform a fresh installation of version 10.2.0.2 or upgrade according to official documentation
  6. Restore any custom configurations and data from the backup
  7. Start the Pentaho server and verify the application functions normally
  8. Confirm that Karaf JMX beans are no longer exposed or require proper authentication by default
Caveat Review release notes for 10.2.0.2 to check for any configuration or feature changes that may require adjustment

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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