Apache NiFi 1.1.0 through 2.7.2 are missing authorization when updating configuration properties on extension components that have specific Required Permissions based on the Restricted annotation. The Restricted annotation indicates additional privileges required to add the annotated component to the flow configuration, but framework authorization did not check restricted status when updating a component previously added. The missing authorization requires a more privileged user to add a restricted component to the flow configuration, but permits a less privileged user to make property configuration changes. Apache NiFi installations that do not implement different levels of 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.8.0 is the recommended mitigation.
oryginał ENCVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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:I/V:C/RE:M/U:AmberApache Nifi
APPApache1.1.0 – 2.8.0 (bez)
Powiązane podatności
Apache NiFi External XML Entity issue in SplitXML processor. Malicious XML content could cause information dis...
A malicious X-ProxyContextPath or X-Forwarded-Context header containing external resources or embedded code co...
In Apache NiFi before 0.7.2 and 1.x before 1.1.2 in a cluster environment, the proxy chain serialization/deser...
Apache NiFi 1.12.0 through 2.9.0 are missing authorization when replacing Process Groups that include extensio...
The optional extension component TinkerpopClientService is missing the Restricted annotation with the Execute ...