CVE-2024-28982
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 10.1.0.0 and 9.3.0.7, including 8.3.x do not correctly protect the ACL service endpoint of the Pentaho User Console against XML External Entity Reference.
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 · moderate confidenceThis is an XML External Entity (XXE) injection vulnerability in the ACL service endpoint of Hitachi Vantara Pentaho Business Analytics Server's User Console. The lack of proper XXE protection allows attackers to exploit XML parsing to potentially read internal files, perform SSRF attacks, or cause denial of service.
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, < 9.3.0.7>= 9.3.1.0, < 10.1.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 the installed Pentaho Business Analytics Server versionCheck the version file in the Pentaho installation directory, review startup logs, or access the About page in the User ConsoleAffected if The installed version is >= 8.3.0 and < 9.3.0.7, OR >= 9.3.1.0 and < 10.1.0.0
-
Locate the ACL service endpointIdentify the ACL service endpoint URL path in the Pentaho User Console configuration (typically under /pentaho/acl or similar ACL-related service paths)Affected if The ACL service endpoint is exposed and accessible over the network
-
Verify XML parsing is enabled for the ACL serviceReview the XML parser configuration files in the Pentaho installation (such as web.xml or pentaho-servlet.xml) to confirm XML external entity processing is not disabled for the ACL endpointAffected if XML parsing is enabled and XXE protection is not configured for the ACL service endpoint
A user is affected if their Pentaho version falls within the affected ranges AND the ACL service endpoint is accessible with XML parsing enabled.
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.710.1.0.0
Upgrade to Pentaho versions 10.1.0.0, 9.3.0.7, or later. If immediate patching is not feasible, restrict network access to the ACL service endpoint and disable XML external entity processing in the XML parser configuration.
10.1.0.0 (or 9.3.0.7 as minimal security patch)
- Back up the Pentaho Business Analytics Server installation and configuration
- Download the fixed version: Pentaho Business Analytics Server 10.1.0.0 (or 9.3.0.7 for minimal update)
- Stop the Pentaho Server service
- Install the fixed version following standard Pentaho upgrade documentation
- Verify the ACL service endpoint is no longer vulnerable to XXE attacks
- Restart the Pentaho Server service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28982 — 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-2024-28982 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