Threats affecting pkg:maven/Apache Software Foundation/org.apache.nifi:nifi-jetty

Apache NiFi version 2.11.0 contains a vulnerability related to improper handling of gzip-encoded HTTP requests. The application REST API disabled support for gzip encoding but did not properly validate multiple Content-Encoding headers or non-standard gzip identifiers. This flaw allows crafted requests to consume excessive memory, leading to potential denial of service. Upgrading to version 2.12.0 mitigates this issue by disabling decompression of gzip-encoded HTTP requests regardless of header variations.

Apache NiFi 0.0.1 through 2.9.0 support building qualified URLs from one of several HTTP request headers that provide an alternative to the standard Host header without validating the values provided. Apache NiFi 1.6.0 introduced a configurable application property to restrict values provided in the HTTP Host header, but did not apply the validation to alternative Proxy and Forwarded headers. The absence of proxy host header validation allowed a client to instruct Apache NiFi web services to construct invalid qualified URLs for redirection or data references. Upgrading to Apache NiFi 2.10.0 is the recommended mitigation, which implements validation for the X-ProxyHost and X-Forwarded-Host HTTP request headers based on the nifi.web.proxy.host property. Enabling header validation requires configuring the application with HTTPS. Reverse proxy servers in front of Apache NiFi are responsible for filtering input request headers and providing allowed values to the application.