Apache NiFi: Potential Code Injection with Database Services using H2
Apache Software Foundation · Apache NiFi
Apache NiFi's DBCPConnectionPool and HikariCPConnectionPool Controller Services contain a code injection flaw in how they handle Database URLs using the H2 driver. An attacker who is an authenticated and authorized user can configure a malicious H2 Database URL that enables execution of custom code.
The DBCPConnectionPool and HikariCPConnectionPool Controller Services in Apache NiFi 0.0.2 through 1.21.0 allow an authenticated and authorized user to configure a Database URL with the H2 driver that enables custom code execution. The resolution validates the Database URL and rejects H2 JDBC locations. You are recommended to upgrade to version 1.22.0 or later which fixes this issue.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (Metasploit) was available the same day.
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
See the family tree4 related vulnerabilities in the same code over 10 weeks. The latest fix listed for nifi-hikari-dbcp-service is 1.23.0.
Same bug familyLinked by evidence that a fix failed or the same code was patched again. Oldest first.
- same familyThis CVECVE-2023-34468NiFi: Potential Code Injection with Database Services using H212 Jun 2023
relatedHigh
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Fixed one release later1.22.0 → 1.23.0 (org.apache.nifi:nifi-hikari-dbcp-service)
- Same code patched: HikariCPConnectionPool.java (machine-matched)commit 4faf3eacommit 5325787
relatedHigh
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Fixed one release later1.23.0 → 1.23.1 (org.apache.nifi:nifi-jms-processors)
- Same code patched: HikariCPConnectionPool.java (machine-matched)commit 5325787commit 064550a
- Similar weakness in the same product (machine-matched)same product + description similarity
Fixes in nifi-hikari-dbcp-serviceMaven package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.
- 1.22.0CVE-2023-3446812 Jun 2023
- 1.23.0CVE-2023-3654229 Jul 2023Latest listed
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linkedNo ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
Am I affected? What do I upgrade to?
From GitHub Security Advisories and OSV3 packages in 1 ecosystem. No single main package: each of these ships the affected code.
- Mavenorg.apache.nifi:nifi-dbcp-baseAffected: 0.0.2 up to 1.22.0Upgrade to 1.22.0 or later
- Mavenorg.apache.nifi:nifi-hikari-dbcp-serviceAffected: 0.0.2 up to 1.22.0Upgrade to 1.23.0 or later
- Mavenorg.apache.nifi:nifi-dbcp-service-narAffected: 0.0.2 up to 1.22.0Upgrade to 1.22.0 or later