CVE-2024-28984
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 · uneditedHitachi Vantara Pentaho Business Analytics Server prior to versions 10.1.0.0 and 9.3.0.7, including 8.3.x allow a malicious URL to inject content into the Analyzer plugin interface.
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 confidenceCross-site scripting (XSS) vulnerability in the Pentaho Business Analytics Server Analyzer plugin allows injection of malicious content through specially crafted URLs. The vulnerability stems from insufficient input validation on URL parameters within the Analyzer interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.3.0.7> 9.3.1.0, < 10.1.0.0CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed Pentaho BA Server versionCheck the version file or system information. The version is typically stored in a version.properties file or displayed in the Pentaho Administration Console. Common locations include the lib directory or systemAbout.html in the web interface.Affected if The installed version is less than 9.3.0.7 OR greater than or equal to 9.3.1.0 but less than 10.1.0.0
-
Confirm the Analyzer plugin is enabledVerify whether the Analyzer plugin is installed and accessible in the Pentaho BI Server. The Analyzer functionality is typically accessed through the Pentaho User Console under the 'Analyze' or 'New Analysis' options.Affected if The Analyzer plugin is present and accessible to users in the Pentaho User Console
-
Check access to Analyzer interface URLsReview the Pentaho web application URLs used to access the Analyzer feature. These typically include paths such as /pentaho/api/repos/analysis or /pentaho/ViewAction?Affected if The Analyzer URL endpoints are reachable without additional authentication layers beyond standard Pentaho credentials
-
Verify URL parameter handling in AnalyzerInspect how the Analyzer plugin handles URL parameters. The vulnerability involves insufficient input validation on URL parameters. If you have access to logs or can test, look for reflected parameters in Analyzer URLs.Affected if URL parameters passed to Analyzer are not being sanitized or validated before being rendered in the interface
You are affected if your Pentaho BA Server version is any version before 9.3.0.7 or between 9.3.1.0 and 10.1.0.0 (exclusive), and the Analyzer plugin is enabled and accessible in your 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 · scoped9.3.0.710.1.0.0
Upgrade Pentaho Business Analytics Server to version 10.1.0.0 or 9.3.0.7 (or later) which contains the patch for this vulnerability. If immediate upgrading is not possible, restrict access to the Analyzer plugin interface as a temporary workaround.
Upgrade to version 10.1.0.0 or 9.3.0.7
- Identify the current Pentaho Business Analytics Server version by checking the server configuration or about page
- Download the appropriate fixed version (9.3.0.7 or 10.1.0.0) from the official Hitachi Vantara support portal at support.pentaho.com
- Back up the existing Pentaho installation directory, configuration files, and any custom content or plugins
- Stop the Pentaho Business Analytics Server service
- Install the new version by replacing the existing files with the downloaded fixed release
- Restore custom configurations and content from the backup if needed
- Start the Pentaho Business Analytics Server service
- Verify the Analyzer plugin loads correctly and test that the XSS vulnerability is no longer present by confirming the URL injection no longer executes arbitrary JavaScript
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28984 — 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-28984 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