LowGHSA-mpj7-7mg7-x95jBIT-nifi-2024-56512CVE-2024-56512

Apache NiFi: Missing Complete Authorization for Parameter and Service References

Published 28 Dec 2024 · Updated 15 Sept 2025

Is your project on an affected org.apache.nifi:nifi-web-api?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=1.10.0 <2.1.0
Fixed in
2.1.0
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.nifi:nifi-web-api -DdepVersion=2.1.0 -DforceVersion=true

Details

Apache NiFi 1.10.0 through 2.0.0 are missing fine-grained authorization checking for Parameter Contexts, referenced Controller Services, and referenced Parameter Providers, when creating new Process Groups.

Creating a new Process Group can include binding to a Parameter Context, but in cases where the Process Group did not reference any Parameter values, the framework did not check user authorization for the bound Parameter Context. Missing authorization for a bound Parameter Context enabled clients to download non-sensitive Parameter values after creating the Process Group.

Creating a new Process Group can also include referencing existing Controller Services or Parameter Providers. The framework did not check user authorization for referenced Controller Services or Parameter Providers, enabling clients to create Process Groups and use these components that were otherwise unauthorized.

This vulnerability is limited in scope to authenticated users authorized to create Process Groups. The scope is further limited to deployments with component-based authorization policies. Upgrading to Apache NiFi 2.1.0 is the recommended mitigation, which includes authorization checking for Parameter and Controller Service references on Process Group creation.

Is GHSA-mpj7-7mg7-x95j in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.nifi:nifi-web-api, and gives you the command that fixes it.

More advisories for org.apache.nifi:nifi-web-api

  • HighCVE-2026-44914Apache NiFi: Missing authorization when replacing Process Groups with restricted components · 22 Jun 2026
  • LowCVE-2026-44911Apache NiFi allows read-only users to submit component configuration verification request · 22 Jun 2026
  • HighCVE-2026-25903Apache NiFi: Missing Authorization of Restricted Permissions for Component Updates · 17 Feb 2026
  • HighCVE-2019-12421Apache NiFi user log out issue · 2 Dec 2019
  • MediumCVE-2019-10083Apache NiFi process group information disclosure · 2 Dec 2019
org.apache.nifi:nifi-web-api security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.