Apache Software Foundation NiFi 2.0.0 Milestone4 Release Candidate 1

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:apache:nifi:2.0.0:milestone4-rc1:*:*:*:*:*:*

part: a version: 2.0.0 update: milestone4-rc1

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductNifi (c50d5476-8f35-5ca2-94ef-ba428d97a1b7)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:apache/nifi purl2cpe 2026-06-01 10:14:28.339194
pkg:docker/apache/nifi purl2cpe 2026-06-01 10:14:28.339196
pkg:github/apache/nifi purl2cpe 2026-06-01 10:14:28.339197
pkg:maven/org.apache.nifi/nifi purl2cpe 2026-06-01 10:14:28.339199

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-52067 vulnerable 2026-06-08 06:52:14.688846 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.
Published: 2024-11-21T09:28:43.910Z
Updated: 2024-11-21T15:37:48.210Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.