GHSA-77hf-23pq-2g7c — nifi-registry-core
HIGHGHSA-77hf-23pq-2g7c is a high-severity (CVSS 8.8) OS Command Injection vulnerability in org.apache.nifi.registry:nifi-registry-core. A fix is available for org.apache.nifi.registry:nifi-registry-core — see the affected versions and patch details below.
Code injection in Apache NiFi and NiFi Registry
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.
How urgent is this, really
GHSA-77hf-23pq-2g7c plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.3org.apache.nifi.registry:nifi-registry-core:1.16.3 |
| ☕Maven | org.apache.nifi:nifi | ≥ 1.10.0&&< 1.16.3 | 1.16.3org.apache.nifi:nifi: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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-77hf-23pq-2g7c can be triaged on real exposure rather than presence alone.
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 Security finds GHSA-77hf-23pq-2g7c across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.