CVE-2019-12421: Apache NiFi user log out issue

Summary

02/12/2019
Yes i
High
8.8

CVE-2019-12421: Apache NiFi user log out issue. Affects org.apache.nifi:nifi-web-security versions >= 1.3.0, < 1.10.0. Fixed in 1.10.0. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache NiFi is an open-source data integration tool that allows users to automate the flow of data between different systems. It provides a web-based interface for designing and managing data flows. NiFi supports various authentication mechanisms, including PKI. However, versions 1.0.0 to 1.9.2 of NiFi have a vulnerability that affects user log out functionality.

Vulnerability Detail

When using an authentication mechanism other than PKI, NiFi versions 1.0.0 to 1.9.2 do not properly invalidate the authentication token on the server side when a user clicks Log Out. Although the client-side token is invalidated, the server-side token remains valid for up to 12 hours. This allows an attacker to use the user's token to make API requests to NiFi, potentially gaining unauthorized access to sensitive data or performing malicious actions.

How To Fix

Minimum fixed version

1.10.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

If upgrading to the latest version is not immediately possible, a workaround is to manually invalidate the authentication token on the server side after the user logs out. This can be done by modifying the NiFi source code or by implementing a custom solution that ensures the server-side token is invalidated when the user logs out.

Conclusion

The Apache NiFi user log out issue (CVE-2019-12421) affects versions 1.0.0 to 1.9.2 of NiFi. It allows an attacker to use a user's authentication token to make unauthorized API requests. To fix this vulnerability, it is recommended to upgrade to NiFi version 1.10.0 or later. If upgrading is not immediately possible, a workaround is available to manually invalidate the authentication token on the server side. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.nifi:nifi-web-security →

Share this vulnerability

FAQ

Apache NiFi is an open-source data integration tool that allows users to automate the flow of data between different systems. It provides a web-based interface for designing and managing data flows.

NiFi versions 1.0.0 to 1.9.2 are affected by this vulnerability.

This vulnerability allows an attacker to use a user's authentication token to make API requests to NiFi, potentially gaining unauthorized access to sensitive data or performing malicious actions.

To fix this vulnerability, it is recommended to upgrade to NiFi version 1.10.0 or later.

If upgrading to the latest version is not immediately possible, a workaround is to manually invalidate the authentication token on the server side after the user logs out.

How To Fix

Minimum fixed version

1.10.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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback