RHSA-2021:2988

csafUSredhat_csaf

Red Hat Security Advisory: varnish:6 security update

view advisory published 2021-08-02

An update for the varnish:6 module is now available for Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8.1 Extended Update Support, and Red Hat Enterprise Linux 8.2 Extended Update Support. Red Hat Product Security has rated this update as having a security impact of Important. 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-2021-36740USmedium6.5—
Varnish Cache, with HTTP/2 enabled, allows request smuggling and VCL authorization bypass via a large Content-Length header for a POST request. This affects Varnish Enterprise 6.0.…
02

references

External citations — patches, advisories, analysis.

03

remediations (156)

  • Fixedvarnish-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.src (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-0:6.0.2-2.module+el8.2.0+11973+a748eca7.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-0:6.0.2-2.module+el8.2.0+11973+a748eca7.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-0:6.0.2-2.module+el8.2.0+11973+a748eca7.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-0:6.0.2-2.module+el8.2.0+11973+a748eca7.src (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-0:6.0.2-2.module+el8.2.0+11973+a748eca7.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.aarch64 (varnish:6) 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-2021:2988
  • Fixedvarnish-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.ppc64le (varnish:6) 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-2021:2988
  • Fixedvarnish-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.s390x (varnish:6) 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-2021:2988
  • Fixedvarnish-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.src (varnish:6) 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-2021:2988
  • Fixedvarnish-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.x86_64 (varnish:6) 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-2021:2988
  • Fixedvarnish-devel-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-devel-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-devel-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-devel-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-devel-0:6.0.2-2.module+el8.2.0+11973+a748eca7.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-devel-0:6.0.2-2.module+el8.2.0+11973+a748eca7.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-devel-0:6.0.2-2.module+el8.2.0+11973+a748eca7.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-devel-0:6.0.2-2.module+el8.2.0+11973+a748eca7.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-devel-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.aarch64 (varnish:6) 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-2021:2988
  • Fixedvarnish-devel-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.ppc64le (varnish:6) 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-2021:2988
  • Fixedvarnish-devel-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.s390x (varnish:6) 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-2021:2988
  • Fixedvarnish-devel-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.x86_64 (varnish:6) 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-2021:2988
  • Fixedvarnish-docs-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-docs-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-docs-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-docs-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-docs-0:6.0.2-2.module+el8.2.0+11973+a748eca7.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-docs-0:6.0.2-2.module+el8.2.0+11973+a748eca7.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-docs-0:6.0.2-2.module+el8.2.0+11973+a748eca7.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-docs-0:6.0.2-2.module+el8.2.0+11973+a748eca7.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-docs-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.aarch64 (varnish:6) 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-2021:2988
  • Fixedvarnish-docs-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.ppc64le (varnish:6) 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-2021:2988
  • Fixedvarnish-docs-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.s390x (varnish:6) 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-2021:2988
  • Fixedvarnish-docs-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.x86_64 (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.src (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.src (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.aarch64 (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.ppc64le (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.s390x (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.src (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.x86_64 (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.aarch64 (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.ppc64le (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.s390x (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-debuginfo-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.x86_64 (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.aarch64 (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.ppc64le (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.s390x (varnish:6) 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-2021:2988
  • Fixedvarnish-modules-debugsource-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.x86_64 (varnish:6) 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-2021:2988
  • Workaroundvarnish-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.src (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.2-2.module+el8.2.0+11973+a748eca7.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.2-2.module+el8.2.0+11973+a748eca7.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.2-2.module+el8.2.0+11973+a748eca7.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.2-2.module+el8.2.0+11973+a748eca7.src (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.2-2.module+el8.2.0+11973+a748eca7.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.src (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.2-2.module+el8.2.0+11973+a748eca7.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.2-2.module+el8.2.0+11973+a748eca7.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.2-2.module+el8.2.0+11973+a748eca7.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.2-2.module+el8.2.0+11973+a748eca7.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-devel-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.2-2.module+el8.1.0+11974+ea5ba4f1.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.2-2.module+el8.2.0+11973+a748eca7.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.2-2.module+el8.2.0+11973+a748eca7.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.2-2.module+el8.2.0+11973+a748eca7.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.2-2.module+el8.2.0+11973+a748eca7.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-docs-0:6.0.6-2.module+el8.4.0+11921+1a6539fc.1.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.src (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.src (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.src (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debuginfo-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.1)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-4.module+el8+2481+4078e9d2.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream EUS (v. 8.2)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.aarch64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.ppc64le (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.s390x (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

  • Workaroundvarnish-modules-debugsource-0:0.15.0-5.module+el8.3.0+6843+b3b42fcc.x86_64 (varnish:6) as a component of Red Hat Enterprise Linux AppStream (v. 8)

    This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

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