cve.bz

CVE-2024-52067 apache nifi

6.9 mediumEPSS 0.7%Fix available

Medium (6.9) in apache nifi. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.nifi:nifi-framework-core 1.28.1, 2.0.0.

On this page
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.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/AU:Y/R:U/V:D/RE:L/U:Green

CVSS 3.1

4.9 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-11-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • org.apache.nifi:nifi-framework-core (Maven): fixed in 1.28.1, 2.0.0

Ask an AI about this CVE

Show the promptExplain CVE-2024-52067 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-52067?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-52067?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-52067 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache NiFifrom 1.16.0 through 1.28.0
Apache Software Foundation Apache NiFifrom 2.0.0-M1 through 2.0.0-M4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v3vc-6qcv-4vrxMavenorg.apache.nifi:nifi-framework-core>=1.16.0 <1.28.11.28.1
GHSA-v3vc-6qcv-4vrxMavenorg.apache.nifi:nifi-framework-core>=2.0.0-M1 <2.0.02.0.0

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON