Cyber Resilience

CVE-2023-3517

Hitachi Pentaho Data Integration And Analytics 1.0 – 9.3.0.5

Published
12 December 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 8.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N
EPSS Score 0.0064 48th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2023-3517 is a high-severity Resource Injection (CWE-99) vulnerability in Hitachi Pentaho Data Integration And Analytics. Its CVSS base score is 8.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Hitachi Vantara Pentaho Data Integration & Analytics versions before 9.5.0.1 and 9.3.0.5, including 8.3.x does not restrict JNDI identifiers during the creation of XActions, allowing control of system level data sources.

CWE(s)
CWE-99NVD-CWE-Other

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-1575Shared CWE-99
CVE-2026-7303Shared CWE-99
CVE-2026-5414Shared CWE-99
CVE-2026-10168Shared CWE-99
CVE-2025-2410Shared CWE-99
CVE-2025-9619Shared CWE-99
CVE-2026-15186Shared CWE-99
CVE-2025-43491Shared CWE-99
CVE-2025-1645Shared CWE-99
CVE-2025-8793Shared CWE-99

Affected Assets

hitachi
pentaho data integration and analytics
1.0 — 9.3.0.5 · 9.4.0.0 — 9.5.0.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.8
  • V1.3.9
  • V1.3.11
  • V9.2.2

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and sanitization that prevent resource-identifier injection flaws.

PR.AA-05 partial match
prevents

Least-privilege access policy and enforcement limits damage from injected resource identifiers even when input validation is absent.

PR.IR-01 partial match
prevents

Network segmentation and unauthorized-access controls reduce the blast radius of successful resource injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect resource-injection flaws but does not itself implement preventive controls.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and resource-identifier sanitization that directly prevents resource injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls on external identifiers used to access resources.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce attack surface for resource injection but do not prescribe identifier validation.

A.8.28 Secure coding partial match
prevents

Secure coding standards require strict validation and whitelisting of all resource identifiers before use.

A.8.3 Information access restriction partial match
mitigates

Information-access-restriction policies limit which resources can be referenced, indirectly reducing injection impact.

References