First published: Tue Apr 28 2020(Updated: )
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.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache NiFi Registry | >=0.1.0<=0.5.0 | |
maven/org.apache.nifi.registry:nifi-registry-web-api | >=0.1.0<=0.5.0 | 0.7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-9482 is a vulnerability in NiFi Registry versions 0.1.0 to 0.5.0 that allows an authenticated user to use their client-side token for up to 12 hours after logging out.
CVE-2020-9482 affects NiFi Registry versions 0.1.0 to 0.5.0 by not invalidating the authentication token on the server side when a user logs out, allowing the client-side token to be used for up to 12 hours.
CVE-2020-9482 has a severity rating of 6.5 (medium).
To fix CVE-2020-9482, upgrade to a version of NiFi Registry above 0.5.0 that includes the security patch.
More information about CVE-2020-9482 can be found on the Apache NiFi Registry security page: [https://nifi.apache.org/registry-security.html#CVE-2020-9482](https://nifi.apache.org/registry-security.html#CVE-2020-9482)