RHSA-2020:5495

csafUSredhat_csaf

Red Hat Security Advisory: nginx:1.16 security update

view advisory published 2020-12-15

An update for the nginx:1.16 module is now available for Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

01

describes (1)

Related CVEs.

IDseverity exploitable
CVE-2019-20372USmedium5.3Exploit
NGINX before 1.17.7, with certain error_page configurations, allows HTTP request smuggling, as demonstrated by the ability of an attacker to read unauthorized web pages in environm…
02

references

External citations — patches, advisories, analysis.

03

remediations (110)

  • Fixednginx-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.src (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-all-modules-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.noarch (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-debugsource-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-debugsource-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-debugsource-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-debugsource-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-filesystem-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.noarch (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-image-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-image-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-image-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-image-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-image-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-image-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-image-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-image-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-perl-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-perl-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-perl-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-perl-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-perl-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-perl-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-perl-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-perl-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-xslt-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-xslt-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-xslt-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-xslt-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-xslt-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-xslt-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-xslt-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-http-xslt-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-mail-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-mail-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-mail-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-mail-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-mail-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-mail-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-mail-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-mail-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-stream-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-stream-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-stream-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-stream-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-stream-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-stream-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-stream-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Fixednginx-mod-stream-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

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

    https://access.redhat.com/errata/RHSA-2020:5495
  • Workaroundnginx-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.src (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-all-modules-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.noarch (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-debugsource-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-debugsource-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-debugsource-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-debugsource-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-filesystem-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.noarch (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-image-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-image-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-image-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-image-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-image-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-image-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-image-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-image-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-perl-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-perl-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-perl-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-perl-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-perl-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-perl-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-perl-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-perl-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-xslt-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-xslt-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-xslt-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-xslt-filter-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-xslt-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-xslt-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-xslt-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-http-xslt-filter-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-mail-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-mail-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-mail-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-mail-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-mail-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-mail-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-mail-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-mail-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-stream-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-stream-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-stream-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-stream-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-stream-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.aarch64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-stream-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.ppc64le (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-stream-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.s390x (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

  • Workaroundnginx-mod-stream-debuginfo-1:1.16.1-1.module+el8.3.0+8844+e5e7039f.1.x86_64 (nginx:1.16) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    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; } }

scry

Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.

Free scan