CVE-2020-9482: Insufficient Session Expiration in Apache NiFi Registry
Summary
CVE-2020-9482: Insufficient Session Expiration in Apache NiFi Registry. Affects org.apache.nifi.registry:nifi-registry-web-api versions >= 0.1.0, < 0.7.0. Fixed in 0.7.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Apache NiFi Registry is an open-source tool that provides a centralized registry for storing, managing, and sharing dataflows, schemas, and other artifacts. It is built on top of Apache NiFi and is designed to provide versioned flow management, deployment, and tracking capabilities. NiFi Registry supports various authentication mechanisms, including PKI. However, versions 0.1.0 to 0.5.0 suffer from an insufficient session expiration vulnerability.
Vulnerability Detail
The vulnerability in Apache NiFi Registry allows an attacker to continue making API requests using a client-side authentication token even after the user has logged out. When a user clicks the 'Log Out' button, the authentication token is invalidated on the client side but not on the server side. This means that an attacker who obtains the token can use it for up to 12 hours after the user has logged out to perform unauthorized actions on the NiFi Registry. The vulnerability has a CVSS score of 6.5, indicating a moderate severity level.
How To Fix
Minimum fixed version
0.7.0
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version to mitigate the risk of unauthorized access to the NiFi Registry.
Conclusion
The insufficient session expiration vulnerability in Apache NiFi Registry allows an attacker to continue making unauthorized API requests using a client-side authentication token. To mitigate this risk, it is crucial to upgrade to NiFi Registry version 0.7.0 or later. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.apache.nifi.registry:nifi-registry-web-api →
FAQ
Apache NiFi Registry is an open-source tool that provides a centralized registry for storing, managing, and sharing dataflows, schemas, and other artifacts.
Versions 0.1.0 to 0.5.0 of NiFi Registry are affected by this vulnerability.
The vulnerability allows an attacker to use a client-side authentication token to make unauthorized API requests to the NiFi Registry for up to 12 hours after the user has logged out.
Yes, upgrading to NiFi Registry version 0.7.0 or later fixes this vulnerability.
No, upgrading to the fixed version is the only way to mitigate the risk of unauthorized access.
