basicsecurity.net
Proof, not just disclosure.
Threats / Hitachi Vantara / CVE-2022-43939
CVE-2022-43939 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-033EPSS 0.92266 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
451 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).
CISA KEV ↗Confirmed
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
Affected: Hitachi Vantara, Pentaho Business Analytics (BA) Server. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-647 CWE-647.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 451 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by HITVAN (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by HITVANCNA
    Credited with finding itHarry Withington, Aura Information Securityfinder