CVE-2024-25617

highPriorität · beachten · 61EPSS 0.881 · 100. PerzentilDEEURUUS

grimoire priorityP1 · Urgent

Exploitable?

—

no known exploitation

Likely / severe?

88.1% (100th) EPSS

CVSS 7.5 · high

Is it mine?

118 products

Prüfe deine Angriffsfläche

Who says so?

6 sources

cnnvd · enisa_euvd · fstec_bdu · cert_bund

EPSS · bewertet 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

Behebungen

Hersteller-Fix, Mitigation oder Workaround, wie von den Quellen veröffentlicht.

Ein Hersteller-Fix ist verfügbar.

Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobenlibecap-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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
Behobensquid-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.

cvss

Technischer Schweregrad, 0–10. Eine Zeile je Quelle.

8.6

010

Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · 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 USAusnutzbarkeit 3.9 · Auswirkung 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.comAusnutzbarkeit 3.9 · Auswirkung 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

SSVC

Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.

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

schwächen

Die CWE-Schwächeklassen, zu denen dies gehört.

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

betroffene Produkte (118)

Betroffene Produkte und Versionsbereiche.

Debian Linuxalle Versionencert_bundDEcpe:/o:debian:debian_linux:-
Open Source CentOSalle Versionencert_bundDEcpe:/o:centos:centos:-
Open Source Squid <6.5alle Versionencert_bundDE
Oracle Linuxalle Versionencert_bundDEcpe:/o:oracle:linux:-
Red Hat Enterprise Linuxalle Versionencert_bundDEcpe:/o:redhat:enterprise_linux:-
SUSE Linuxalle Versionencert_bundDEcpe:/o:suse:suse_linux:-
Ubuntu Linuxalle Versionencert_bundDEcpe:/o:canonical:ubuntu_linux:-
Open Source Squid< 6.5cert_bundDE
squid-cache squidalle Versionenenisa_euvdEU
squid-cache squid≤ < 6.5enisa_euvdEU
Squid Software Foundation Squid≤ 6.5fstec_bduRU
АО «ИВК» Альт 8 СПalle Versionenfstec_bduRU
АО «НТЦ ИТ РОСА» РОСА Кобальт≤ 7.9fstec_bduRU
ООО «РусБИТех-Астра» Astra Linux Common Edition≤ 1.6 «Смоленск»fstec_bduRU
ООО «РусБИТех-Астра» Astra Linux Special Edition≤ 1.7fstec_bduRU
ООО «РусБИТех-Астра» Astra Linux Special Edition≤ 4.7fstec_bduRU
netapp bluexpalle VersionennvdUScpe:2.3:a:netapp:bluexp:*:*:*:*:*:*:*:*
squid-cache squid3.0 → 6.5nvdUScpe:2.3:a:squid-cache:squid:*:*:*:*:*:*:*:*
libecap-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)alle Versionenfixedredhat_csafUS
libecap-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)alle Versionenfixedredhat_csafUS

20 von 118 angezeigt

Advisories (6)

Hersteller- und Ökosystem-Meldungen dazu.

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

auch bekannt als (3)

Weitere Namen und Kennungen dieser Entität.

quellen

Welche Quellen diesen Datensatz belegen und wann.

cnnvd enisa_euvd fstec_bdu cert_bund nvd redhat_csaf NVD CVE.org MITRE

veröffentlicht 2024-02-14geändert 2026-06-17

Referenzen (12)

Externe Belege — Patches, Meldungen, Analysen.

scry

Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan