CVE-2020-24669
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 New Analysis Report in Hitachi Vantara Pentaho through 7.x - 8.x contains a DOM-based Cross-site scripting vulnerability, which allows an authenticated remote users to execute arbitrary JavaScript code. Specifically, the vulnerability lies in the 'Analysis Report Description' field in 'About this Report' section. Remediated in >= 8.3.0.9, >= 9.0.0.1, and >= 9.1.0.0 GA.
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 confidenceDOM-based Cross-site scripting (XSS) vulnerability in Hitachi Vantara Pentaho's Analysis Report feature. The 'Analysis Report Description' field in the 'About this Report' section does not properly sanitize user input, allowing authenticated users to inject and execute arbitrary JavaScript code in the context of other users' browsers.
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>= 7.0.0, < 8.3.0.9>= 9.0.0, < 9.0.0.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed Pentaho versionLocate the Pentaho version through the administration console (typically at /pentaho/admin) or check version files in the Pentaho installation directory. The version is often displayed in the server startup logs or in a VERSION.txt file within the installation root.Affected if The installed version falls within 7.0.0 through 8.3.0.8, or 9.0.0.0 exactly (prior to 9.0.0.1). Compare your version number against these ranges.
-
Confirm the Analysis Report feature is in useNavigate to the Analysis Report functionality within the Pentaho user interface. Access the 'About this Report' section where the Description field is located. Check if any reports have been created that include descriptions.Affected if The Analysis Report feature is active and contains reports with descriptions that could be viewed by other users.
-
Inspect existing report descriptions for injection payloadsReview all entries in the 'Analysis Report Description' field across all reports. Look for HTML script tags, JavaScript event handlers (onload, onerror, onmouseover), or other suspicious script-related patterns in the description content.Affected if Any description field contains unencoded HTML script tags or JavaScript code that could execute in a browser.
-
Check browser console for XSS errorsIf you have access to a web browser interacting with the Pentaho Analysis Report feature, open the developer console and navigate to reports with descriptions. Look for any script execution errors or unexpected JavaScript behavior.Affected if JavaScript executes unexpectedly or errors appear in the console when viewing report descriptions.
Your environment is affected if you are running Pentaho version 7.0.0 through 8.3.0.8 or version 9.0.0.0, and the Analysis Report feature with Description fields is accessible to authenticated users.
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.
From vendor data8.3.0.99.0.0.1
Upgrade Pentaho to version 8.3.0.9 or higher, 9.0.0.1 or higher, or 9.1.0.0 or higher. Apply input validation and output encoding on the Analysis Report Description field as a defense-in-depth measure if running legacy versions.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24669 — 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-2020-24669 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