Threats / Hitachi Vantara / CVE-2022-43939
CVE-2022-43939
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Hitachi Vantara Pentaho Business Analytics (BA) Server vulnerability
Hitachi Vantara Pentaho BA Server uses non-canonical URL paths for authorization decisions, allowing attackers to bypass access controls.
Verdict
Today item — known-exploited.
An attacker can exploit improper URL canonicalization in authorization logic to gain unauthorized access to protected resources in Pentaho BA Server. This vulnerability has been actively exploited in the wild.
CISA KEV Yes · 2025-03-035EPSS 0.92266 (verify live)6Exploit Weaponized · public PoC7CVSS 8.63CISA SSVC Exploitation: active · Automatable: yes · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
483 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-03-03).
Probability (EPSS)
EPSS 0.92266 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H) · Affected: Hitachi Vantara, Pentaho Business Analytics (BA) Server. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-647 CWE-647.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 700 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
WeaknessCWE-647 · CWE-647
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft requests using non-canonical URL paths (such as double-encoded characters or path traversal sequences) that the authorization mechanism fails to normalize before checking permissions.
Business
Unauthorized users gain access to sensitive business analytics data, dashboards, and reports without proper authentication or authorization controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I bypass role-based access controls by submitting requests with obfuscated URL paths that pass through the authorization filter but resolve to protected endpoints.
Business
Confidential business intelligence, financial data, and operational metrics become accessible to unauthorized personnel, creating compliance violations and competitive risk.
3
Lateral reach — past segmentation narrative 3
Attacker
I escalate privileges by accessing administrative functions through canonicalization bypasses, allowing me to modify system configurations or create new privileged accounts.
Business
System integrity is compromised, enabling potential data manipulation, deletion, or deployment of persistent backdoors for long-term unauthorized access.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by HITVANCNA
Credited with finding itHarry Withington, Aura Information Securityfinder
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.