Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

org.apache.nifi:nifi-framework-core

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.9MavenPublished

    Apache NiFi: Potential Insertion of Sensitive Parameter Values in Debug Log

    CVE-2024-52067 · GHSA-v3vc-6qcv-4vrx

    Affected
    • Maven org.apache.nifi:nifi-framework-core >= 1.16.0, < 1.28.1; >= 2.0.0-M1, <= 2.0.0-M4
    Fixed in
    2.0.01.28.1· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 2.0.0 or 1.28.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5MavenPublished

    Insertion of Sensitive Information into Log File in Apache NiFi

    CVE-2020-1942 · GHSA-7q8g-gpfp-v8gx

    Affected
    • Maven org.apache.nifi:nifi-framework-core >= 0.0.1, <= 1.11.0
    Fixed in
    1.12.0-RC1· Vendor fix available
    Issue
    In Apache NiFi 0.0.1 to 1.11.0, the flow fingerprint factory generated flow fingerprints which included sensitive property descriptor values. In the event a node attempted to join a cluster and the cluster flow was not inheritable, the flow fingerprint of both the cluster and local flow was printed, potentially containing sensitive values in plaintext.

    Recommended action: Upgrade to 1.12.0-RC1 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →