basicsecurity.net
Proof, not just disclosure.
Threats / Hitachi Vantara / CVE-2022-43769
CVE-2022-43769 · 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 contains a template injection vulnerability allowing attackers to execute arbitrary commands via malicious Spring templates in properties files.

Verdict

Today item — known-exploited.

An unauthenticated or low-privileged attacker can inject Spring Expression Language templates into configuration properties, achieving remote code execution on the affected server. The high EPSS score and active exploitation indicate immediate risk.

CISA KEV Yes · 2025-03-033EPSS 0.9767 (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
4 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.9767 — 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-74 CWE-74 — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-74 · CWE-74Injection
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 identify that Pentaho BA Server processes user-controllable properties files without proper sanitization of template expressions.
Business
Attackers gain a direct path to remote code execution without requiring valid credentials or complex exploitation chains.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I craft a malicious properties file containing Spring template syntax designed to execute system commands when the server parses the configuration.
Business
The server executes arbitrary commands with the privileges of the Pentaho process, compromising data confidentiality and system integrity.
3

Lateral reach — past segmentation narrative 3

Attacker
I establish persistent access or pivot to connected systems and data repositories managed by the analytics platform.
Business
Attackers gain control over business intelligence infrastructure, sensitive analytics data, and potentially connected enterprise systems.
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)
  • 4 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