Summary
Apache NiFi: Potential Insertion of Sensitive Parameter Values in Debug Log
Apache NiFi 1.16.0 through 1.28.0 and 2.0.0-M1 through 2.0.0-M4 include optional debug logging of Parameter Context values during the flow synchronization process. An authorized administrator with access to change logging levels could enable debug logging for framework flow synchronization, causing the application to write Parameter names and values to the application log. Parameter Context values may contain sensitive information depending on application flow configuration. Deployments of Apache NiFi with the default Logback configuration do not log Parameter Context values. Upgrading to Apache NiFi 2.0.0 or 1.28.1 is the recommendation mitigation, eliminating Parameter value logging from the flow synchronization process regardless of the Logback configuration.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.apache.nifi:nifi-framework-core to 1.28.1 or later; org.apache.nifi:nifi-framework-core to 2.0.0 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-52067? CVE-2024-52067 is a medium-severity security vulnerability in org.apache.nifi:nifi-framework-core (maven), affecting versions >= 1.16.0, < 1.28.1. It is fixed in 1.28.1, 2.0.0.
- Which versions of org.apache.nifi:nifi-framework-core are affected by CVE-2024-52067? org.apache.nifi:nifi-framework-core (maven) versions >= 1.16.0, < 1.28.1 is affected.
- Is there a fix for CVE-2024-52067? Yes. CVE-2024-52067 is fixed in 1.28.1, 2.0.0. Upgrade to this version or later.
- Is CVE-2024-52067 exploitable, and should I be worried? Whether CVE-2024-52067 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-52067 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-52067?
- Upgrade
org.apache.nifi:nifi-framework-coreto 1.28.1 or later - Upgrade
org.apache.nifi:nifi-framework-coreto 2.0.0 or later
- Upgrade