If NiFi Registry 0.1.0 to 0.5.0 uses an authentication mechanism other than PKI, when the user clicks Log Out, NiFi Registry 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 Registry.
Advisories
Source ID Title
EUVD EUVD EUVD-2022-1170 If NiFi Registry 0.1.0 to 0.5.0 uses an authentication mechanism other than PKI, when the user clicks Log Out, NiFi Registry 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 Registry.
Github GHSA Github GHSA GHSA-rcwj-2hj2-vmjj Insufficient Session Expiration in Apache NiFi Registry
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2024-08-04T10:26:16.177Z

Reserved: 2020-03-01T00:00:00

Link: CVE-2020-9482

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2020-04-28T19:15:12.470

Modified: 2024-11-21T05:40:44.190

Link: CVE-2020-9482

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.