Search for packages
| purl | pkg:maven/org.apache.nifi/nifi-web-api@1.1.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-mrb8-sr51-vkep
Aliases: CVE-2019-12421 GHSA-fmqw-vqh5-cwq9 |
Apache NiFi user log out issue When using an authentication mechanism other than PKI, when the user clicks Log Out in NiFi versions 1.0.0 to 1.9.2, NiFi invalidates the authentication token on the client side but not on the server side. This permits the user's client-side token to be used for up to 12 hours after logging out to make API requests to NiFi. |
Affected by 2 other vulnerabilities. |
|
VCID-y19q-bhcy-nqdk
Aliases: CVE-2026-25903 GHSA-c5w7-m8wf-xc77 |
Apache NiFi: Missing Authorization of Restricted Permissions for Component Updates 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. |
Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||