Apache NiFi 1.12.0 through 2.9.0 are missing authorization when replacing Process Groups that include extension components with specific Required Permissions based on the Restricted annotation. The Restricted annotation indicates additional privileges required, but framework authorization did not check restricted status when handling requests to replace Process Groups. The missing authorization permits a user with general write access to add components with Restricted status. Apache NiFi installations that do not implement specific authorization for Restricted components are not subject to this vulnerability because the framework enforces write permissions as the security boundary. Upgrading to Apache NiFi 2.9.0 is the recommended mitigation, which removes the implementation of Restricted status authorization from the framework.
oryginał ENCVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:U/V:C/RE:L/U:ClearApache Nifi
APPApache1.12.0 – 2.10.0 (bez)
Powiązane podatności
Apache NiFi: XXE w procesorze SplitXML umożliwia RCE lub ujawnienie danych
RCE przez nagłówek X-ProxyContextPath w Apache NiFi
Apache NiFi — injection przez deserializację łańcucha proxy w klastrze
Apache NiFi: nieautoryzowana walidacja Parameter Context przez użytkownika read-only
Apache NiFi: atak typu zip bomb przez gzip-encoded HTTP request