`CVE-2023-34468` Apache NiFi

Affected software	Apache NiFi
Severity	8.8 High CVSS 3.1 2 scores
Fixed in	`1.22.0`
Weakness	Code injection (CWE-94)
Published	12 Jun 2023
Updated	17 Jun 2026

Description

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.

Exploitation status

Working exploit published

A reviewed exploit catalogue lists ready-to-run exploit code for this CVE.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment exploitation: none
Indexed PoC 8 indexed Published artifacts you can open, in GitHub PoC, Metasploit; first seen 2023-11-25.
EPSS 62% chance in 30 days A model's forecast, not a report of exploitation. Higher than 99% of all scored CVEs.

5 of these are GitHub repositories with fewer than 5 stars. They are listed for reference and don't count toward the exploitation status above.

Index	Artifact	Stars	First seen
GitHub PoC	CVE-2023-34468: Remote Code Execution via DB Components in Apache NiFi	8	2023-11-25
GitHub PoC	PoC exploit for CVE-2023-34468 — RCE via H2 RUNSCRIPT in Apache NiFi <= 1.21.0	5	2026-05-10
GitHub PoC	CVE-2023-34468 - Apache NiFi H2 RCE PoC	1	2026-05-10
GitHub PoC	CVE-2023-34468: Apache NiFi 1.21.0 Remote Code Execution (ExecuteProcess Variant) - Security Research & Analysis by Mohammed Moshii		2026-11-07
GitHub PoC	Writeup of the Hackthebox Helix machine		2026-09-09
GitHub PoC	CVE-2023-34468 Apache NiFi ExecuteSQL H2 RUNSCRIPT RCE PoC		2026-07-12
GitHub PoC	Educational proof-of-concept for CVE-2023-34468 affecting Apache NiFi. Demonstrates H2 JDBC URL abuse leading to authenticated RCE in vulnerable NiFi versions.		2026-06-16
Metasploit	Apache NiFi H2 Connection String Remote Code Execution (excellent rank)

Index

Artifact

Stars

First seen

GitHub PoC

CVE-2023-34468: Remote Code Execution via DB Components in Apache NiFi

2023-11-25

GitHub PoC

PoC exploit for CVE-2023-34468 — RCE via H2 RUNSCRIPT in Apache NiFi <= 1.21.0

2026-05-10

GitHub PoC

CVE-2023-34468 - Apache NiFi H2 RCE PoC

2026-05-10

GitHub PoC

CVE-2023-34468: Apache NiFi 1.21.0 Remote Code Execution (ExecuteProcess Variant) - Security Research & Analysis by Mohammed Moshii

2026-11-07

GitHub PoC

Writeup of the Hackthebox Helix machine

2026-09-09

GitHub PoC

CVE-2023-34468 Apache NiFi ExecuteSQL H2 RUNSCRIPT RCE PoC

2026-07-12

GitHub PoC

Educational proof-of-concept for CVE-2023-34468 affecting Apache NiFi. Demonstrates H2 JDBC URL abuse leading to authenticated RCE in vulnerable NiFi versions.

2026-06-16

Metasploit

Apache NiFi H2 Connection String Remote Code Execution (excellent rank)

Waratek protection

Mitigation candidate

A kind of vulnerability Waratek's rules address, with exploit code published or exploitation reported. No rule exists and none is planned yet. The decision below says what we found to build a rule from.

Protection none
Action unverified
Review automated Inferred
Record active

Decided by	The affected package being open source on Maven, so the fix can be read
Finding	This CVE affects an open-source Java library published on Maven Central (Maven packages: org.apache.nifi:nifi-dbcp-base, org.apache.nifi:nifi-hikari-dbcp-service, org.apache.nifi:nifi-dbcp-service-nar), so it is squarely in ARMR's territory and the source needed to understand the defect is public. That makes it a candidate for an ARMR patch rule. No rule exists and none is scheduled: the diff between the affected and fixed versions has not been read, and a closer look may find no hook point ARMR can act on.

Decided by

The affected package being open source on Maven, so the fix can be read

Finding

This CVE affects an open-source Java library published on Maven Central (Maven packages: org.apache.nifi:nifi-dbcp-base, org.apache.nifi:nifi-hikari-dbcp-service, org.apache.nifi:nifi-dbcp-service-nar), so it is squarely in ARMR's territory and the source needed to understand the defect is public. That makes it a candidate for an ARMR patch rule. No rule exists and none is scheduled: the diff between the affected and fixed versions has not been read, and a closer look may find no hook point ARMR can act on.

CVSS

8.8 HIGH v3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

Version Score Band Vector Assigner Type

CVSS 3.1 8.8 HIGH CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H NVD Primary published

CVSS 3.1 8.8 HIGH CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CISA-ADP Secondary

Version	Score	Band	Vector	Assigner	Type
CVSS 3.1	8.8	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`	NVD	Primary	published
CVSS 3.1	8.8	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`	CISA-ADP	Secondary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev

Package Introduced Fixed Last affected

org.apache.nifi:nifi-dbcp-base 0.0.2 1.22.0 unbounded

org.apache.nifi:nifi-hikari-dbcp-service 0.0.2 1.22.0 unbounded

org.apache.nifi:nifi-dbcp-service-nar 0.0.2 1.22.0 unbounded

Package	Introduced	Fixed	Last affected
`org.apache.nifi:nifi-dbcp-base`	0.0.2	`1.22.0`	unbounded
`org.apache.nifi:nifi-hikari-dbcp-service`	0.0.2	`1.22.0`	unbounded
`org.apache.nifi:nifi-dbcp-service-nar`	0.0.2	`1.22.0`	unbounded

Products and versions

4 products, 4 version entries

Source	Vendor	Product	Scheme	Affected versions
nvd	apache	nifi	generic	≥ 0.0.2 and ＜ 1.22.0
osv	org.apache.nifi	nifi-dbcp-base	generic	≥ 0.0.2 and ＜ 1.22.0
osv	org.apache.nifi	nifi-dbcp-service-nar	generic	≥ 0.0.2 and ＜ 1.22.0
osv	org.apache.nifi	nifi-hikari-dbcp-service	generic	≥ 0.0.2 and ＜ 1.22.0

Source

Vendor

Product

Scheme

Affected versions

nvd

apache

nifi

generic

≥ 0.0.2 and ＜ 1.22.0

osv

org.apache.nifi

nifi-dbcp-base

generic

≥ 0.0.2 and ＜ 1.22.0

osv

org.apache.nifi

nifi-dbcp-service-nar

generic

≥ 0.0.2 and ＜ 1.22.0

osv

org.apache.nifi

nifi-hikari-dbcp-service

generic

≥ 0.0.2 and ＜ 1.22.0

References

URL	Tags
https://github.com/apache/nifi/pull/7349	WEB
https://github.com/apache/nifi/commit/4faf3ea59895e7e153db3f8f61147ff70a254361	WEB
https://exceptionfactory.com/posts/2023/10/07/firsthand-analysis-of-apache-nifi-vulnerability-cve-2023-34468	WEB
https://github.com/apache/nifi	PACKAGE
https://issues.apache.org/jira/browse/NIFI-11653	WEB
https://lists.apache.org/thread/7b82l4f5blmpkfcynf3y6z4x1vqo59h8	WEB
https://nifi.apache.org/security.html#CVE-2023-34468	WEB
https://www.cyfirma.com/outofband/apache-nifi-cve-2023-34468-rce-vulnerability-analysis-and-exploitation	WEB
http://packetstormsecurity.com/files/174398/Apache-NiFi-H2-Connection-String-Remote-Code-Execution.html	WEB
http://www.openwall.com/lists/oss-security/2023/06/12/3	WEB

URL

Timeline

Published	2023-06-12	By the CVE Program.
NVD record modified	2026-06-17	NVD's own last-modified date for this record.

Published

2023-06-12

By the CVE Program.

NVD record modified

2026-06-17

NVD's own last-modified date for this record.

How VRT decided (17 of 24 rules ran)

17 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification no match A researcher's recorded decision for this specific CVE

5 manual classification no match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side no match Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven matched In scope Maven packages: org.apache.nifi:nifi-dbcp-base, org.apache.nifi:nifi-hikari-dbcp-service, org.apache.nifi:nifi-dbcp-service-nar

10 cna-maven-package not reached An affected Maven artifact named by the CNA itself

11 known-cpe-product not reached An NVD CPE naming a product ARMR tracks

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint no match A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

18 open-source-maven decided it matched Mitigation candidate Open-source Maven artifact indexed by OSV (Maven packages: org.apache.nifi:nifi-dbcp-base, org.apache.nifi:nifi-hikari-dbcp-service, org.apache.nifi:nifi-dbcp-service-nar). The source is public, which makes an ARMR patch rule a candidate; nothing here establishes that one can be written.

19 poc-derivable skipped An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit skipped Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

21 secure-rule-match no match A vulnerability class already blocked by an ARMR security rule

22 exploited-no-fix-or-poc skipped Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold no match Severity is HIGH — only MEDIUM/LOW are deprioritized

24 no-exploit-published no match A CISA or VulnCheck KEV listing, a CISA verdict of active exploitation, a reviewed exploit catalogue, or a GitHub PoC with 5 or more stars carries this CVE — exploit code is in use or published, so it stays a candidate

Products the scope rules checked

The products this CVE's record names, and whether VRT tracks each one. The scope rules decided on these.

Vendor Product Tracked CPE Source

apache nifi tracked cpe:2.3:a:apache:nifi:*:*:*:*:*:*:*:* yaml

NVD ↗ · CVE.org ↗