RHSA-2020:5495

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }

To mitigate this issue, use a named location instead of having the error_page handler do the redirect, this configuration is not vulnerable to request smuggling on all versions of NGINX we tested. server { listen 80; server_name localhost; error_page 401 @401; location / { return 401; } location @401 { return 302 http://example.org; } }