CVE-2024-25617

highpriority · attend · 61EPSS 0.881 · 100 %ileDEEURUUS
grimoire priorityP1 · Urgent
Exploitable?
—
no known exploitation
Likely / severe?
88.1% (100th) EPSS
CVSS 7.5 · high
Is it mine?
118 products
Check your exposure
Who says so?
6 sources
cnnvd · enisa_euvd · fstec_bdu · cert_bund

EPSS · scored 2026-10-27

Squid is an open source caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. Due to a Collapse of Data into Unsafe Value bug ,Squid may be vulnerable to a Denial of Service attack against HTTP header parsing. This problem allows a remote client or a remote server to perform Denial of Service when sending oversized headers in HTTP messages. In versions of Squid prior to 6.5 this can be achieved if the request_header_max_size or reply_header_max_size settings are unchanged from the default. In Squid version 6.5 and later, the default setting of these parameters is safe. Squid will emit a critical warning in cache.log if the administrator is setting these parameters to unsafe values. Squid will not at this time prevent these settings from being changed to unsafe values. Users are advised to upgrade to version 6.5. There are no known workarounds for this vulnerability. This issue is also tracked as SQUID-2024:2

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

  • Fixedlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.src (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.src (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-debuginfo-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-debuginfo-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-debuginfo-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-debuginfo-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-debugsource-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-debugsource-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-debugsource-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedsquid-debugsource-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1062
  • Fixedlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.src (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-7:4.15-3.module+el8.6.0+21376+425c674a.5.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-7:4.15-3.module+el8.6.0+21376+425c674a.5.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-7:4.15-3.module+el8.6.0+21376+425c674a.5.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-7:4.15-3.module+el8.6.0+21376+425c674a.5.src (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-7:4.15-3.module+el8.6.0+21376+425c674a.5.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-debuginfo-7:4.15-3.module+el8.6.0+21376+425c674a.5.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-debuginfo-7:4.15-3.module+el8.6.0+21376+425c674a.5.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-debuginfo-7:4.15-3.module+el8.6.0+21376+425c674a.5.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-debuginfo-7:4.15-3.module+el8.6.0+21376+425c674a.5.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-debugsource-7:4.15-3.module+el8.6.0+21376+425c674a.5.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-debugsource-7:4.15-3.module+el8.6.0+21376+425c674a.5.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-debugsource-7:4.15-3.module+el8.6.0+21376+425c674a.5.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-debugsource-7:4.15-3.module+el8.6.0+21376+425c674a.5.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1066
  • Fixedsquid-7:5.5-5.el9_2.5.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-7:5.5-5.el9_2.5.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-7:5.5-5.el9_2.5.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-7:5.5-5.el9_2.5.src as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-7:5.5-5.el9_2.5.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-debuginfo-7:5.5-5.el9_2.5.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-debuginfo-7:5.5-5.el9_2.5.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-debuginfo-7:5.5-5.el9_2.5.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-debuginfo-7:5.5-5.el9_2.5.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-debugsource-7:5.5-5.el9_2.5.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-debugsource-7:5.5-5.el9_2.5.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-debugsource-7:5.5-5.el9_2.5.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-debugsource-7:5.5-5.el9_2.5.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1184
  • Fixedsquid-7:3.5.20-17.el7_9.10.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-7:3.5.20-17.el7_9.10.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-7:3.5.20-17.el7_9.10.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-7:3.5.20-17.el7_9.10.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-7:3.5.20-17.el7_9.10.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-debuginfo-7:3.5.20-17.el7_9.10.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-debuginfo-7:3.5.20-17.el7_9.10.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-debuginfo-7:3.5.20-17.el7_9.10.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-debuginfo-7:3.5.20-17.el7_9.10.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-debuginfo-7:3.5.20-17.el7_9.10.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-debuginfo-7:3.5.20-17.el7_9.10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-debuginfo-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-debuginfo-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-debuginfo-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-debuginfo-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-migration-script-7:3.5.20-17.el7_9.10.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-migration-script-7:3.5.20-17.el7_9.10.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-migration-script-7:3.5.20-17.el7_9.10.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-migration-script-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-migration-script-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-sysvinit-7:3.5.20-17.el7_9.10.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-sysvinit-7:3.5.20-17.el7_9.10.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-sysvinit-7:3.5.20-17.el7_9.10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-sysvinit-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Fixedsquid-sysvinit-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2024:1787
  • Workaroundlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.src (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.src (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:4.15-6.module+el8.8.0+21374+5b4927f1.4.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.8)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.src (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debuginfo-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-debugsource-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundlibecap-devel-0:1.0.1-2.module+el8.1.0+4044+36416a77.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:4.15-3.module+el8.6.0+21376+425c674a.5.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:4.15-3.module+el8.6.0+21376+425c674a.5.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:4.15-3.module+el8.6.0+21376+425c674a.5.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:4.15-3.module+el8.6.0+21376+425c674a.5.src (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:4.15-3.module+el8.6.0+21376+425c674a.5.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:4.15-3.module+el8.6.0+21376+425c674a.5.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:4.15-3.module+el8.6.0+21376+425c674a.5.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:4.15-3.module+el8.6.0+21376+425c674a.5.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:4.15-3.module+el8.6.0+21376+425c674a.5.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:4.15-3.module+el8.6.0+21376+425c674a.5.aarch64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:4.15-3.module+el8.6.0+21376+425c674a.5.ppc64le (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:4.15-3.module+el8.6.0+21376+425c674a.5.s390x (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:4.15-3.module+el8.6.0+21376+425c674a.5.x86_64 (squid:4) as a component of Red Hat Enterprise Linux AppStream EUS (v.8.6)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:5.5-5.el9_2.5.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:5.5-5.el9_2.5.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:5.5-5.el9_2.5.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:5.5-5.el9_2.5.src as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:5.5-5.el9_2.5.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:5.5-5.el9_2.5.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:5.5-5.el9_2.5.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:5.5-5.el9_2.5.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:5.5-5.el9_2.5.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:5.5-5.el9_2.5.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:5.5-5.el9_2.5.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:5.5-5.el9_2.5.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debugsource-7:5.5-5.el9_2.5.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:3.5.20-17.el7_9.10.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:3.5.20-17.el7_9.10.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:3.5.20-17.el7_9.10.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:3.5.20-17.el7_9.10.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:3.5.20-17.el7_9.10.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:3.5.20-17.el7_9.10.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:3.5.20-17.el7_9.10.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:3.5.20-17.el7_9.10.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:3.5.20-17.el7_9.10.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:3.5.20-17.el7_9.10.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:3.5.20-17.el7_9.10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-debuginfo-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-migration-script-7:3.5.20-17.el7_9.10.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-migration-script-7:3.5.20-17.el7_9.10.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-migration-script-7:3.5.20-17.el7_9.10.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-migration-script-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-migration-script-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-sysvinit-7:3.5.20-17.el7_9.10.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-sysvinit-7:3.5.20-17.el7_9.10.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-sysvinit-7:3.5.20-17.el7_9.10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-sysvinit-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

  • Workaroundsquid-sysvinit-7:3.5.20-17.el7_9.10.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf

    To mitigate this flaw in Squid versions prior to 6.5, set the request_header_max_size and reply_header_max_size configuration options to 21KB. The following lines should be added to the Squid configuration file: ~~~ request_header_max_size 21 KB reply_header_max_size 21 KB ~~~ In Squid versions 6.5 and newer, the default values of these options are considered safe and the above configuration can be removed. Also, Squid will emit a warning in the logs if the configured values are unsafe.

02

cvss

Technical severity, 0–10. One row per scoring source.

8.6
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5.3–8.6

v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hprimary · NVD / NIST USexploitability 3.9 · impact 3.6
v3.18.6highAV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:Hsecondary · FSTEC (BDU) RU
v3.15.3mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lsecondary · ENISA EU
v3.15.3mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lsecondary · security-advisories@github.comexploitability 3.9 · impact 1.4
v3.17.5highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:Hsecondary · CVSS-BT (t0sche)
v3.18.6highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:Hsecondary · Red Hat Product Security US
03

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: none · Automatable: yes · Technical Impact: partialcoordinatorcisa_ssvcUS
04

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-182USCWE-182USCWE-182USCWE-400USCWE-400US
05

affected products (118)

Products and version ranges known to be affected.

showing 20 of 118
06

advisories (6)

Vendor and ecosystem advisories describing this.

  • RHSA-2024:1062Red Hat Security Advisory: squid:4 security update2024-03-01csaf · redhat_csafUS

    An update for the squid:4 module is now available for Red Hat Enterprise Linux 8.8 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.

  • RHSA-2024:1066Red Hat Security Advisory: squid:4 security update2024-03-04csaf · redhat_csafUS

    An update for the squid:4 module is now available for Red Hat Enterprise Linux 8.6 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.

  • RHSA-2024:1184Red Hat Security Advisory: squid security update2024-03-06csaf · redhat_csafUS

    An update for squid is now available for Red Hat Enterprise Linux 9.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.

  • RHSA-2024:1787Red Hat Security Advisory: squid security update2024-04-11csaf · redhat_csafUS

    An update for squid is now available for Red Hat Enterprise Linux 7. 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.

  • WID-SEC-W-2024-0396Squid: Schwachstelle ermöglicht Denial of ServiceDeutsch2024-02-14csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Squid ausnutzen, um einen Denial of Service Angriff durchzuführen.

  • WID-SEC-W-2024-1248Xerox FreeFlow Print Server: Mehrere SchwachstellenDeutsch2024-05-28csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität des Systems zu gefährden

07

also known as (3)

Other names and identifiers for this entity.

08

sources

Which sources assert this record, and when.

cnnvdenisa_euvdfstec_bducert_bundnvdredhat_csafNVDCVE.orgMITRE
published 2024-02-14modified 2026-06-17
09

references (12)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan