GHSA-23qf-3jf9-h3q9
MEDIUMApache NiFi Insufficient Property Validation vulnerability
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
org.apache.nifi:nifi-dbcp-base☕org.apache.nifi:nifi-jms-processors☕org.apache.nifi:nifi-dbcp-service-api☕org.apache.nifi:nifi-dbcp-service-bundleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Apache NiFi 1.21.0 through 1.23.0 support JDBC and JNDI JMS access in several Processors and Controller Services with connection URL validation that does not provide sufficient protection against crafted inputs. An authenticated and authorized user can bypass connection URL validation using custom input formatting. The resolution enhances connection URL validation and introduces validation for additional related properties. Upgrading to Apache NiFi 1.23.1 is the recommended mitigation.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.nifi:nifi-dbcp-base | ≥ 1.21.0&&< 1.23.1 | 1.23.1 |
| ☕Maven | org.apache.nifi:nifi-jms-processors | ≥ 1.21.0&&< 1.23.1 | 1.23.1 |
| ☕Maven | org.apache.nifi:nifi-dbcp-service-api | ≥ 1.21.0&&< 1.23.1 | 1.23.1 |
| ☕Maven | org.apache.nifi:nifi-dbcp-service-bundle | ≥ 1.21.0&&< 1.23.1 | 1.23.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.nifi:nifi-dbcp-base. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.nifi:nifi-dbcp-base to 1.23.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-23qf-3jf9-h3q9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-23qf-3jf9-h3q9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-23qf-3jf9-h3q9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-23qf-3jf9-h3q9 in your dependencies?
O3 detects GHSA-23qf-3jf9-h3q9 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.