CVE-2020-24666
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 Analysis Report in Hitachi Vantara Pentaho through 7.x - 8.x contains a stored Cross-site scripting vulnerability, which allows an authenticated remote users to execute arbitrary JavaScript code. Specifically, the vulnerability lies in the 'Display Name' parameter. Remediated in >= 9.1.0.1
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in Hitachi Vantara Pentaho's Analysis Report feature. The vulnerability is present in the 'Display Name' parameter, which fails to properly sanitize user-supplied input before rendering it in web pages. An authenticated remote attacker can embed malicious JavaScript code within the Display Name field, which will execute in the browsers of other users who view the Analysis Report.
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, < 9.1.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 installed Pentaho versionCheck the Pentaho server version by reviewing server logs, the pentaho-server directory, or the Pentaho Administration Console. Common locations include version files in the installation directory or the 'VERSION' file typically found in the server root.Affected if The installed version is >= 7.0.0 and < 9.1.0.1, placing it within the vulnerable range.
-
Confirm Analysis Report feature is accessibleVerify that the Analysis Report feature is enabled and accessible within the Pentaho user interface. Check user permissions and feature flags in the Pentaho configuration.Affected if The Analysis Report feature is enabled and available to authenticated users, providing an attack surface for the vulnerability.
-
Review Display Name entries in Analysis ReportsExamine the Analysis Report configurations for any Display Name fields that may contain user-supplied content. Query the Pentaho database or review configuration files where Display Names are stored, looking for suspicious patterns such as <script> tags, javascript: URIs, or HTML event handlers.Affected if Any Display Name field contains unencoded HTML, JavaScript code, or HTML event handler attributes that could execute in a user's browser.
You are affected if your Pentaho version falls within 7.0.0 through 9.1.0.0 and the Analysis Report feature is accessible with Display Name fields containing potentially malicious script content.
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 data9.1.0.1
Upgrade Pentaho to version 9.1.0.1 or later, which contains the fix for this vulnerability. As a compensating control, implement strict input validation and output encoding on all user-supplied fields, particularly those displayed in web interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24666 — 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-24666 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