CVE-2022-43938
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 9.4.0.1 and 9.3.0.2, including 8.3.x cannot allow a system administrator to disable scripting capabilities of Pentaho Reports (*.prpt) through the JVM script manager.
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 confidencePentaho Business Analytics Server prior to versions 9.4.0.1 and 9.3.0.2 lacks the ability for administrators to disable scripting capabilities in Pentaho Report files (*.prpt) through the JVM script manager. This missing control could allow remote attackers to execute arbitrary code via malicious scripts embedded in report files.
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.2= 9.4.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Pentaho BA Server versionCheck the version file or startup logs for Pentaho Business Analytics Server. Common locations include version.info in the installation directory or server startup logs.Affected if Version is less than 9.3.0.2 or equal to 9.4.0.0 (these versions lack the scripting disable capability)
-
Verify JVM script manager configurationInspect the Pentaho configuration files for JVM script manager settings. Look for any property or option that controls scripting in Pentaho Report files (*.prpt).Affected if No configuration option exists to disable scripting in .prpt files through the JVM script manager (this control is missing in vulnerable versions)
-
Confirm scripting is enabled by defaultReview the Pentaho administration interface or configuration for script execution settings in report processing.Affected if There is no way to disable script execution in .prpt files through the JVM script manager interface
The environment is affected if the installed Pentaho version is less than 9.3.0.2 or equals 9.4.0.0 and there is no ability to disable scripting capabilities in Pentaho Report files through the JVM script manager.
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.2
Upgrade to Pentaho Business Analytics Server versions 9.4.0.1, 9.3.0.2, or later which introduce the capability to disable scripting in Pentaho Reports (*.prpt) through the JVM script manager.
Pentaho Business Analytics Server 9.3.0.2+ or 9.4.0.1+ (recommend latest stable 9.4.x release)
- 1. Back up your current Pentaho Business Analytics Server installation and configuration
- 2. Download Pentaho Business Analytics Server version 9.3.0.2 or later (9.3.x series), OR version 9.4.0.1 or later (9.4.x series)
- 3. Stop the Pentaho BA Server service
- 4. Install the new version following the standard upgrade procedure documented in the Pentaho documentation
- 5. Restore your custom configurations from the backup
- 6. Start the Pentaho BA Server service
- 7. Verify that scripting capabilities can now be disabled through the JVM script manager for Pentaho Reports (*.prpt)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43938 — 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-2022-43938 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