CVE-2022-43939: Hitachi Vantara Pentaho BA Server Authorization Bypass Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Hitachi Vantara Pentaho Business Analytics Server versions before 9.4.0.1 and 9.3.0.2, including 8.3.x contain security restrictions using non-canonical URLs which can be circumvented.
Description quoted from the CVE record (assigned by HITVAN, published 2023-04-03).
Weakness: CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality low, integrity low, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: partial.
- On CISA KEV since
- 2025-03-03
- US federal deadline
- 2025-03-24
- Ransomware use
- Not known
Public exploit evidence (Exploit Observer)
Also known as: BDU:2023-01993, CNNVD-202304-081, EDB-51350, EUVD-2022-46909, GHSA-r7cq-76xj-2g24
VEDAS cluster: VEDAS:BURNINGBETTA
Exploit Observer links 7 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (7)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Exploit-DB: https://www.exploit-db.com/raw/51350
- Nuclei template: https://raw.githubusercontent.com/projectdiscovery/nuclei-templates/main/http/cves/2022/CVE-2022-43939.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/nuclei/2022/CVE-2022-43939.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/nuclei/2022/CVE-2022-43939.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2022/CVE-2022-43939.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2022/CVE-2022-43939.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2022/CVE-2022-43939.rules
Research and write-ups (1)
Vulnerability databases and vendor advisories (6)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://access.redhat.com/security/cve/cve-2022-43939
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2022-46909
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-r7cq-76xj-2g24
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2022-43939
- Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-43939
- Vulnerability database or vendor advisory: https://www.cnnvd.org.cn/home/globalSearch?keyword=CNNVD-202304-081
25 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.923
very likely to be attacked soon - VEDAS
- 0.989
strong exploit evidence - On CISA KEV
- Yes, since 2025-03-03
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Hitachi Vantara Pentaho Business Analytics Server | from 1.0 before 9.3.0.2 from 9.4.0.0 before 9.4.0.1 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: hitachi vantara_pentaho_business_analytics_server, hitachi,_ltd. hitachi_vantara_pentaho_business_analytics_server.
How to fix it
Fixed versions stated in the CVE record: 9.3.0.2, 9.4.0.1.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor guidance:
- https://support.pentaho.com/hc/en-us/articles/14455394120333--Resolved-Pentaho-BA-Server-Use-of-Non-Canonical-URL-Paths-for-Authorization-Decisions-Versions-before-9-4-0-1-and-9-3-0-2-including-8-3-x-Impacted-CVE-2022-43939-
- https://nvd.nist.gov/vuln/detail/CVE-2022-43939
How to detect it
Nuclei template (active check)
Hitachi Vantara Pentaho Business Analytics - Authentication Bypass
Hitachi Vantara Pentaho Business Analytics Server versions before 9.4.0.1 and 9.3.0.2, including 8.3.x contain security restrictions using non-canonical URLs which can be circumvented.
Name and description quoted from the template, written by VEDAS.
The template sends 2 requests (GET /pentaho/Login, GET /pentaho/api/ldap/config/ldapTreeNodeChildren/require.js); it decides using dsl, status, word matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.
Run it against a host you own or are authorised to test:
nuclei -u https://your-host -t CVE-2022-43939.yamlShow the template (56 lines)
id: CVE-2022-43939
info:
name: "Hitachi Vantara Pentaho Business Analytics - Authentication Bypass"
author: vedas-arpsyndicate
severity: high
description: |
Hitachi Vantara Pentaho Business Analytics Server versions before 9.4.0.1 and 9.3.0.2, including 8.3.x contain
security restrictions using non-canonical URLs which can be circumvented.
reference:
- https://www.exploit.observer/?keyword=CVE-2022-43939&match=exact
- https://subdomain.center/?engine=ammonites&keyword=pentaho&match=exact
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
cvss-score: 8.6
cve-id: CVE-2022-43939
cwe-id: CWE-647
metadata:
verified: false
tags: cve,cve2022,pentaho,hitachi,auth-bypass,vkev,kev,vuln
flow: http(1) && http(2)
http:
- method: GET
path:
- '{{BaseURL}}/pentaho/Login'
matchers:
- type: dsl
dsl:
- 'status_code == 200'
- 'contains(body, "Pentaho User Console - Login")'
condition: and
internal: true
- method: GET
path:
- "{{BaseURL}}/pentaho/api/ldap/config/ldapTreeNodeChildren/require.js"
matchers-condition: and
matchers:
- type: word
part: header
words:
- 'Path=/pentaho'
- 'application/json'
condition: and
- type: word
part: body
words:
- '{}'
- type: status
status:
- 200
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2022-43939 Hitachi Vantara Pentaho Business Analytics - Authentication Bypass. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2022-43939 Hitachi Vantara Pentaho Business Analytics - Authentication Bypass"; flow:established,to_server; http.uri; content:"/pentaho/api/ldap/config/ldapTreeNodeChildren/require.js"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2022-43939; reference:url,https://www.exploit.observer/?keyword=CVE-2022-43939&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=pentaho&match=exact; sid:1008784; rev:1;)
CVE-2022-43939.rules on GitHub
References
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-43939 (government-resource)
Other references
- https://support.pentaho.com/hc/en-us/articles/14455394120333--Resolved-Pentaho-BA-Server-Use-of-Non-Canonical-URL-Paths-for-Authorization-Decisions-Versions-before-9-4-0-1-and-9-3-0-2-including-8-3-x-Impacted-CVE-2022-43939-
- http://packetstormsecurity.com/files/172296/Pentaho-Business-Server-Authentication-Bypass-SSTI-Code-Execution.html
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.