← Back

Nifi

nifi

Vendor: Apache • 50 CVEs

CVEs (50)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Apache
1Nifi
Nov 21, 2024
May 23, 2018
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
Apache NiFi External XML Entity issue in SplitXML processor. Malicious XML content could cause information disclosure or remote code execution. The fix to disable external general entity parsing and disallow doctype decl...Show more
Apache NiFi External XML Entity issue in SplitXML processor. Malicious XML content could cause information disclosure or remote code execution. The fix to disable external general entity parsing and disallow doctype declarations was applied on the Apache NiFi 1.6.0 release. Users running a prior 1.x release should upgrade to the appropriate release.Show less
1Apache
1Nifi
Nov 21, 2024
Jan 25, 2018
N/A· v4
5.0 MEDIUM· v3
3.5 LOW· v2
Any authenticated user (valid client certificate but without ACL permissions) could upload a template which contained malicious code and caused a denial of service via Java deserialization attack. The fix to properly han...Show more
Any authenticated user (valid client certificate but without ACL permissions) could upload a template which contained malicious code and caused a denial of service via Java deserialization attack. The fix to properly handle Java deserialization was applied on the Apache NiFi 1.4.0 release. Users running a prior 1.x release should upgrade to the appropriate release.Show less
1Apache
1Nifi
Nov 21, 2024
Jan 23, 2018
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
A malicious X-ProxyContextPath or X-Forwarded-Context header containing external resources or embedded code could cause remote code execution. The fix to properly handle these headers was applied on the Apache NiFi 1.5.0...Show more
A malicious X-ProxyContextPath or X-Forwarded-Context header containing external resources or embedded code could cause remote code execution. The fix to properly handle these headers was applied on the Apache NiFi 1.5.0 release. Users running a prior 1.x release should upgrade to the appropriate release.Show less
1Apache
1Nifi
Nov 21, 2024
Jan 23, 2018
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
A malicious host header in an incoming HTTP request could cause NiFi to load resources from an external server. The fix to sanitize host headers and compare to a controlled whitelist was applied on the Apache NiFi 1.5.0...Show more
A malicious host header in an incoming HTTP request could cause NiFi to load resources from an external server. The fix to sanitize host headers and compare to a controlled whitelist was applied on the Apache NiFi 1.5.0 release. Users running a prior 1.x release should upgrade to the appropriate release.Show less
1Apache
1Nifi
May 13, 2026
Oct 19, 2017
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
In Apache NiFi before 0.7.2 and 1.x before 1.1.2 in a cluster environment, the proxy chain serialization/deserialization is vulnerable to an injection attack where a carefully crafted username could impersonate another u...Show more
In Apache NiFi before 0.7.2 and 1.x before 1.1.2 in a cluster environment, the proxy chain serialization/deserialization is vulnerable to an injection attack where a carefully crafted username could impersonate another user and gain their permissions on a replicated request to another node.Show less
1Apache
1Nifi
May 13, 2026
Oct 19, 2017
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
In Apache NiFi before 0.7.2 and 1.x before 1.1.2 in a cluster environment, if an anonymous user request is replicated to another node, the originating node identity is used rather than the "anonymous" user.
1Apache
1Nifi
May 13, 2026
Oct 19, 2017
N/A· v4
5.4 MEDIUM· v3
3.5 LOW· v2
In Apache NiFi before 1.0.1 and 1.1.x before 1.1.1, there is a cross-site scripting vulnerability in connection details dialog when accessed by an authorized user. The user supplied text was not being properly handled wh...Show more
In Apache NiFi before 1.0.1 and 1.1.x before 1.1.1, there is a cross-site scripting vulnerability in connection details dialog when accessed by an authorized user. The user supplied text was not being properly handled when added to the DOM.Show less
1Apache
1Nifi
May 13, 2026
Oct 10, 2017
N/A· v4
6.5 MEDIUM· v3
4.0 MEDIUM· v2
An authorized user could upload a template which contained malicious code and accessed sensitive files via an XML External Entity (XXE) attack. The fix to properly handle XML External Entities was applied on the Apache N...Show more
An authorized user could upload a template which contained malicious code and accessed sensitive files via an XML External Entity (XXE) attack. The fix to properly handle XML External Entities was applied on the Apache NiFi 1.4.0 release. Users running a prior 1.x release should upgrade to the appropriate release.Show less
1Apache
1Nifi
May 13, 2026
Jun 12, 2017
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
Apache NiFi before 0.7.4 and 1.x before 1.3.0 need to establish the response header telling browsers to only allow framing with the same origin.
1Apache
1Nifi
May 13, 2026
Jun 12, 2017
N/A· v4
6.1 MEDIUM· v3
4.3 MEDIUM· v2
In Apache NiFi before 0.7.4 and 1.x before 1.3.0, there are certain user input components in the UI which had been guarding for some forms of XSS issues but were insufficient.