CVE-2022-4815
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 versions before 9.4.0.1 and 9.3.0.3, including 8.3.x deserialize untrusted JSON data without constraining the parser to approved classes and methods.
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 confidenceHitachi Vantara Pentaho Business Analytics Server deserializes untrusted JSON data without constraining the parser to approved classes and methods. This allows attackers to potentially instantiate arbitrary classes during deserialization, leading to remote code execution. The vulnerability affects versions before 9.4.0.1 and 9.3.0.3, including 8.3.x.
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>= 8.3.0.0, <= 8.3.0.25>= 9.3.0.0, <= 9.3.0.3= 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 installed Pentaho versionCheck the version file in the Pentaho installation directory. Common locations: pentaho/system/version.properties or pentaho/pentaho-version.txt. Run: cat <pentaho-home>/system/version.properties or check the startup logs.Affected if The installed version falls within 8.3.0.0-8.3.0.25, 9.3.0.0-9.3.0.3, or equals 9.4.0.0
-
Confirm Business Analytics Server componentVerify the Pentaho BA Server is installed. Check for the presence of the BA Server web application: look for pentaho.war or pentaho-server directory, or check the application name in the running web server (typically at /pentaho context path).Affected if The BA Server component is present and running as a web application
-
Identify exposed API endpoints accepting JSONReview web.xml or examine the pentaho-solutions/system directory for exposed REST endpoints and web services. Check for JSON-consuming endpoints in the pentaho-server/tomcat/webapps/pentaho/WEB-INF/web.xml or the API documentation.Affected if The server exposes HTTP endpoints that accept JSON payload (especially /api/ or /pentaho/api/ endpoints)
-
Check for unsafe Jackson or JSON deserialization configurationInspect configuration files for JSON processing libraries. Look for ObjectMapper configurations in pentaho-server/tomcat/webapps/pentaho/WEB-INF/classes or within pentaho-solutions/system/ directory. Search for files containing 'jackson' or 'json' related configuration and check for presence of 'defaultTyping' or similar unsafe settings.Affected if Jackson or JSON deserialization is configured without explicit type whitelisting or with enableDefaultTyping() present
-
Verify network accessibility of vulnerable endpointsCheck if the Pentaho BA Server web interface is exposed to untrusted networks. Review firewall rules, tomcat server.xml bindings, and reverse proxy configurations to determine if HTTP ports (typically 8080 or 8443) are accessible from outside trusted networks.Affected if The Pentaho web interface is reachable from untrusted network segments
You are affected if your Pentaho BA Server version is 8.3.0.0-8.3.0.25, 9.3.0.0-9.3.0.3, or 9.4.0.0 AND the JSON web API endpoints are network-accessible.
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 · scopedUpgrade Pentaho Business Analytics Server to version 9.4.0.1 or 9.3.0.3 or later. If immediate patching is not possible, restrict network access to the server and implement additional monitoring for deserialization-based attack patterns.
Pentaho BA Server: upgrade to 9.4.0.1 or later (9.4.x), or 9.3.0.4 or later (9.3.x); Pentaho 8.3.x: contact vendor for fixed 8.3.x version
- 1. Identify the exact version of Pentaho currently installed by checking the version information in the Pentaho UI or configuration files.
- 2. For Pentaho Business Analytics Server 9.4.0.0: Upgrade to version 9.4.0.1 or later.
- 3. For Pentaho Business Analytics Server 9.3.x: Upgrade to version 9.3.0.4 or later.
- 4. For Pentaho 8.3.x (8.3.0.0 - 8.3.0.25): Upgrade to a version beyond 8.3.0.25 (contact Hitachi Vantara support for the specific fixed version in the 8.3.x line).
- 5. After upgrade, verify the Pentaho services start successfully and the web interface is accessible.
- 6. Test critical workflows to ensure functionality is maintained after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4815 — 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-4815 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