CVE-2024-52067 [Medium] | Information Disclosure in Nifi

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.04%	0.72%	+0.68%
2	2025-12-29	0.19%	0.04%	-0.14%
3	2025-11-21	—	0.19%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.04%

0.72%

+0.68%

2025-12-29

0.19%

0.04%

-0.14%

2025-11-21

—

0.19%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.9	4.0	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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:D/RE:L/U:Green` Click to expand Attack vector (AV:L) Attacker needs local access on the target system. Attack complexity (AC:L) Exploitation conditions are straightforward and stable. Attack requirements (AT:P) Additional preconditions must be present for exploitation. Privileges required (PR:H) High privileges are required. User interaction (UI:N) No user interaction is required. Vulnerable system confidentiality impact (VC:H) High confidentiality impact on the vulnerable system. Vulnerable system integrity impact (VI:L) Limited integrity impact on the vulnerable system. Vulnerable system availability impact (VA:N) No availability impact on the vulnerable system. Subsequent system confidentiality impact (SC:H) High confidentiality impact on subsequent systems. Subsequent system integrity impact (SI:L) Limited integrity impact on subsequent systems. Subsequent system availability impact (SA:N) No availability impact on subsequent systems. Exploit maturity (threat) (E:X) Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked). Confidentiality requirement (CR:X) Not defined: insufficient information; scoring treats this like High (worst case). Integrity requirement (IR:X) Not defined: insufficient information; scoring treats this like High (worst case). Availability requirement (AR:X) Not defined: insufficient information; scoring treats this like High (worst case). Modified attack vector (MAV:X) Not defined: scoring uses the Base Attack Vector (AV). Modified attack complexity (MAC:X) Not defined: scoring uses the Base Attack Complexity (AC). Modified attack requirements (MAT:X) Not defined: scoring uses the Base Attack Requirements (AT). Modified privileges required (MPR:X) Not defined: scoring uses the Base Privileges Required (PR). Modified user interaction (MUI:X) Not defined: scoring uses the Base User Interaction (UI). Modified vulnerable system confidentiality impact (MVC:X) Not defined: scoring uses the Base VC metric. Modified vulnerable system integrity impact (MVI:X) Not defined: scoring uses the Base VI metric. Modified vulnerable system availability impact (MVA:X) Not defined: scoring uses the Base VA metric. Modified subsequent system confidentiality impact (MSC:X) Not defined: scoring uses the Base SC metric. Modified subsequent system integrity impact (MSI:X) Not defined: scoring uses the Base SI metric. Modified subsequent system availability impact (MSA:X) Not defined: scoring uses the Base SA metric. Safety (supplemental) (S:X) Not evaluated. Automatable (supplemental) (AU:Y) Yes: all four kill-chain steps (reconnaissance, weaponization, delivery, exploitation) can be automated. Recovery (supplemental) (R:U) User: manual user intervention is needed to recover services. Value density (supplemental) (V:D) Diffuse: a single exploit event controls relatively limited resources (e.g., one client). Vulnerability response effort (supplemental) (RE:L) Low/trivial response effort (documentation, simple configuration, low-touch guidance). Provider urgency (supplemental) (U:GREEN) Green: provider rates reduced urgency.	—	—	[email protected]
4.9	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	1.2	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.9

4.0

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:D/RE:L/U:Green

Click to expand

Attack vector (AV:L): Attacker needs local access on the target system.
Attack complexity (AC:L): Exploitation conditions are straightforward and stable.
Attack requirements (AT:P): Additional preconditions must be present for exploitation.
Privileges required (PR:H): High privileges are required.
User interaction (UI:N): No user interaction is required.
Vulnerable system confidentiality impact (VC:H): High confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:L): Limited integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:N): No availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:H): High confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:L): Limited integrity impact on subsequent systems.
Subsequent system availability impact (SA:N): No availability impact on subsequent systems.
Exploit maturity (threat) (E:X): Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X): Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X): Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X): Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X): Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X): Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X): Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X): Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X): Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X): Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X): Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X): Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X): Not evaluated.
Automatable (supplemental) (AU:Y): Yes: all four kill-chain steps (reconnaissance, weaponization, delivery, exploitation) can be automated.
Recovery (supplemental) (R:U): User: manual user intervention is needed to recover services.
Value density (supplemental) (V:D): Diffuse: a single exploit event controls relatively limited resources (e.g., one client).
Vulnerability response effort (supplemental) (RE:L): Low/trivial response effort (documentation, simple configuration, low-touch guidance).
Provider urgency (supplemental) (U:GREEN): Green: provider rates reduced urgency.

—

[email protected]

4.9

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

1.2

3.6

[email protected]

Affected software / configurations for CVE-2024-52067

Vendor	Product	Version	Raw CPE
apache	nifi	>= 1.16.0, < 1.28.1	cpe:2.3:a:apache:nifi::::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone1::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone1-rc1::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone1-rc2::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone1-rc3::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone1-rc4::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone1-rc5::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone1-rc6::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone2::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone2-rc1::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone2-rc2::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone2-rc3::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone2-rc4::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone3::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone3-rc1::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone4::::::
apache	nifi	2.0.0	cpe:2.3:a:apache:nifi:2.0.0:milestone4-rc1::::::

References for CVE-2024-52067

URL	Tags
https://lists.apache.org/thread/9rz5rwn2zc7pfjq7ppqldqlc067tlcwd	Mailing List
http://www.openwall.com/lists/oss-security/2024/11/20/2	Mailing List

URL

CVE-2024-52067 | Apache NiFi: Potential Insertion of Sensitive Parameter Values in Debug Log

Exploit prediction scoring system (EPSS) score for CVE-2024-52067

Common vulnerability scoring system (CVSS) metrics for CVE-2024-52067

Weakness enumeration for CVE-2024-52067

GitHub Security Advisory for CVE-2024-52067

Affected software / configurations for CVE-2024-52067

References for CVE-2024-52067