CVE-2023-34468

HIGHNVD 8.88.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 64% probability of exploitation within the next 30 days (top 0.9% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
8.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 64%
CISA-KEV: Not listedEPSS: 64%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.9(high)
EG Risk
66(Track)
EG Risk 66/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity89% × 45%
Exploitation65% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.1%
KEV
Not listed

Published

June 12, 2023

Last Modified

February 13, 2025

References (10)

Affected Packages

(3 across 1 ecosystem)
Maven(3)
PackageVulnerable rangeFixed inDependents
org.apache.nifi:nifi-dbcp-base1.19.0, 1.19.1, 1.20.0, 1.21.01.22.0—
org.apache.nifi:nifi-dbcp-service-nar0.2.0-incubating ... 1.9.2 (57 versions)1.22.0—
org.apache.nifi:nifi-hikari-dbcp-service1.16.0 ... 1.21.0 (10 versions)1.22.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:23 UTCEG score recompute▲ 0.10
  2. 2026-07-22 23:10 UTCEG score recompute
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-20 17:06 UTCEPSS rescore
  5. 2026-07-18 10:03 UTCEPSS rescore
  6. 2026-07-18 10:03 UTCEPSS rescore
  7. 2026-07-15 18:19 UTCOSV refresh
  8. 2026-07-15 16:56 UTCEPSS rescore
  9. 2026-07-15 16:56 UTCEPSS rescore
  10. 2026-07-15 01:58 UTCEPSS rescore
  11. 2026-07-15 01:58 UTCEPSS rescore
  12. 2026-07-13 22:28 UTCEPSS rescore
  13. 2026-07-13 22:28 UTCEPSS rescore
  14. 2026-07-13 06:11 UTCEPSS rescore
  15. 2026-07-13 06:11 UTCEPSS rescore
  16. 2026-07-12 05:45 UTCEPSS rescore
  17. 2026-07-11 08:26 UTCEPSS rescore
  18. 2026-07-11 08:25 UTCEPSS rescore
  19. 2026-07-09 19:08 UTCEPSS rescore
  20. 2026-07-09 19:08 UTCEPSS rescore
  21. 2026-07-05 02:29 UTCEPSS rescore
  22. 2026-07-02 16:59 UTCEPSS rescore
  23. 2026-07-01 15:04 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-28 04:55 UTCEPSS rescore
Show 41 more
  1. 2026-06-27 18:34 UTCOSV refresh
  2. 2026-06-27 03:07 UTCEPSS rescore
  3. 2026-06-27 03:07 UTCEPSS rescore
  4. 2026-06-25 13:48 UTCEPSS rescore
  5. 2026-06-25 13:48 UTCEPSS rescore
  6. 2026-06-24 14:04 UTCEPSS rescore
  7. 2026-06-24 14:03 UTCEPSS rescore
  8. 2026-06-23 21:31 UTCEPSS rescore
  9. 2026-06-23 21:31 UTCEPSS rescore
  10. 2026-06-21 01:58 UTCEPSS rescore
  11. 2026-06-21 01:58 UTCEPSS rescore
  12. 2026-06-18 17:51 UTCEPSS rescore
  13. 2026-06-18 17:51 UTCEPSS rescore
  14. 2026-06-17 17:51 UTCEPSS rescore
  15. 2026-06-17 17:51 UTCEPSS rescore
  16. 2026-06-15 17:47 UTCEPSS rescore
  17. 2026-06-14 23:16 UTCEPSS rescore
  18. 2026-06-13 22:59 UTCEPSS rescore
  19. 2026-06-13 22:59 UTCEPSS rescore
  20. 2026-06-12 23:10 UTCEPSS rescore
  21. 2026-06-12 23:10 UTCEPSS rescore
  22. 2026-06-10 22:17 UTCEPSS rescore
  23. 2026-06-10 05:47 UTCOSV refresh
  24. 2026-06-07 15:23 UTCEPSS rescore
  25. 2026-06-07 15:23 UTCEPSS rescore
  26. 2026-06-06 13:46 UTCEPSS rescore
  27. 2026-06-06 13:46 UTCEPSS rescore
  28. 2026-06-05 06:09 UTCEPSS rescore
  29. 2026-06-05 06:09 UTCEPSS rescore
  30. 2026-06-04 13:11 UTCEPSS rescore
  31. 2026-06-04 13:11 UTCEPSS rescore
  32. 2026-06-01 13:51 UTCEPSS rescore
  33. 2026-06-01 13:51 UTCEPSS rescore
  34. 2026-05-31 22:30 UTCEPSS rescore
  35. 2026-05-31 22:29 UTCEPSS rescore
  36. 2026-05-31 22:29 UTCEPSS rescore
  37. 2026-05-31 00:15 UTCEPSS rescore
  38. 2026-05-31 00:15 UTCEPSS rescore
  39. 2026-05-29 13:43 UTCEPSS rescore
  40. 2026-05-29 13:43 UTCEPSS rescore
  41. 2026-05-24 23:40 UTCEG score recompute

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCsbouabid-sec/CVE-2023-34468-POC
    First seen May 10, 2026

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

    Open source ↗
  • GitHub PoCmbadanoiu/CVE-2023-34468
    First seen Nov 25, 2023

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

    Open source ↗
  • Metasploitexploit/linux/http/apache_nifi_h2_rce✓ verified
    First seen Jun 12, 2023

    Apache NiFi H2 Connection String Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-34468?
CVE-2023-34468 is a high vulnerability published on June 12, 2023. 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…
When was CVE-2023-34468 disclosed?
CVE-2023-34468 was first published in the National Vulnerability Database on June 12, 2023, with the most recent update on February 13, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-34468 actively exploited?
CVE-2023-34468 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-34468?
CVE-2023-34468 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2023-34468?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-34468, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-34468

Explore →

Is Your Infrastructure Affected by CVE-2023-34468?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs