GHSA-77hf-23pq-2g7c
HIGHGHSA-77hf-23pq-2g7c is a high-severity (CVSS 8.8) OS Command Injection vulnerability in org.apache.nifi.registry:nifi-registry-core. O3 Security confirms whether GHSA-77hf-23pq-2g7c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Code injection in Apache NiFi and NiFi Registry
Blast Radius
org.apache.nifi.registry:nifi-registry-core☕org.apache.nifi:nifiReal-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
The optional ShellUserGroupProvider in Apache NiFi 1.10.0 to 1.16.2 and Apache NiFi Registry 0.6.0 to 1.16.2 does not neutralize arguments for group resolution commands, allowing injection of operating system commands on Linux and macOS platforms. The ShellUserGroupProvider is not included in the default configuration. Command injection requires ShellUserGroupProvider to be one of the enabled User Group Providers in the Authorizers configuration. Command injection also requires an authenticated user with elevated privileges. Apache NiFi requires an authenticated user with authorization to modify access policies in order to execute the command. Apache NiFi Registry requires an authenticated user with authorization to read user groups in order to execute the command. The resolution removes command formatting based on user-provided arguments.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.nifi.registry:nifi-registry-core | ≥ 0.6.0&&< 1.16.3 | 1.16.3 |
| ☕Maven | org.apache.nifi:nifi | ≥ 1.10.0&&< 1.16.3 | 1.16.3 |
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.registry:nifi-registry-core. 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.registry:nifi-registry-core to 1.16.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-77hf-23pq-2g7c 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-77hf-23pq-2g7c 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-77hf-23pq-2g7c. 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-77hf-23pq-2g7c in your dependencies?
O3 detects GHSA-77hf-23pq-2g7c across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.