dbcve.org
Pentaho Business AnalyticsApplication · Hitachivantara

CVE-2022-3695

MEDIUM · 6.1 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 8.3.0.27 / 9.2.0.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Hitachi Vantara Pentaho Business Analytics Server prior to versions 9.3.0.0, 9.2.0.4 and 8.3.0.27 allow a malicious URL to inject content into a dashboard when the CDE plugin is present.   

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 contains a cross-site scripting (XSS) vulnerability where a malicious URL can inject arbitrary content into a dashboard when the CDE (Community Dashboard Editor) plugin is present. The vulnerability stems from insufficient input validation/sanitization of URL parameters before rendering content in dashboards.

MitigationUpgrade Pentaho Business Analytics Server to version 9.3.0.0, 9.2.0.4, 8.3.0.27 or later. If upgrading is not immediately feasible, consider disabling the CDE plugin or implementing URL filtering at the web application firewall (WAF) level as a temporary measure.

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
Pentaho Business AnalyticsApplication
Affected:< 8.3.0.27>= 9.2.0.0, < 9.2.0.4

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pentaho Business Analytics Server version
    Locate the version file or startup banner. Typically found in the server installation directory, such as version.info or displayed in the server startup logs. Consult your Pentaho documentation for the exact location in your deployment.
    Affected if version is below 8.3.0.27, or between 9.2.0.0 and 9.2.0.4 (exclusive)
  2. Verify CDE plugin presence
    Check if the Community Dashboard Editor (CDE) plugin is installed and enabled on the Pentaho server. This is typically found in the pentaho-solutions/system directory or through the Pentaho administration console.
    Affected if CDE plugin is installed and enabled on the server
  3. Confirm URL parameter handling in dashboards
    Review dashboard configurations that accept URL parameters. Examine the CDE dashboard definitions to see if URL parameters are rendered directly without sanitization.
    Affected if URL parameters from user input are rendered in dashboards without input validation

Server is affected if it runs a vulnerable Pentaho version (below 8.3.0.27 or 9.2.0.0-9.2.0.4) AND has the CDE plugin enabled, allowing unsanitized URL parameters to be injected into dashboards.

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
Upgrade available Upgrade to 8.3.0.27 / 9.2.0.4 or later
Fixed in 8.3.0.279.2.0.4
Interim mitigation

Upgrade Pentaho Business Analytics Server to version 9.3.0.0, 9.2.0.4, 8.3.0.27 or later. If upgrading is not immediately feasible, consider disabling the CDE plugin or implementing URL filtering at the web application firewall (WAF) level as a temporary measure.

Recommended fix High confidence

Upgrade to version 9.3.0.0, 9.2.0.4, or 8.3.0.27 depending on your current major branch

  1. 1. Back up your current Pentaho Business Analytics installation, including the pentaho.war/biserver-ee and any custom configurations
  2. 2. Download the appropriate fixed version based on your current major version (9.3.0.0, 9.2.0.4, or 8.3.0.27) from the official Hitachi Vantara support portal
  3. 3. Stop the Pentaho Server service
  4. 4. Replace the existing installation files with the new version, preserving your custom configuration files and content repositories
  5. 5. Restart the Pentaho Server
  6. 6. Verify the CDE plugin loads correctly and test that XSS payloads can no longer be injected via URL parameters into dashboards

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

Fix this in Pentaho Business Analytics Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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