Red Hat Security Advisory: squid security update
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.
beschreibt (1)
Zugehörige CVEs.
| ID | Schweregrad | ausnutzbar | ||
|---|---|---|---|---|
| CVE-2024-25617US | high7.5 | — | ||
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 Ser… | ||||
Referenzen
Externe Belege — Patches, Meldungen, Analysen.
Behebungen (26)
- Behobensquid-7:5.5-5.el9_2.5.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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 - Workaroundsquid-7:5.5-5.el9_2.5.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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.
Advisories wie diese benennen die exponierten Produkte, die Angreifer auf Ihrer Angriffsfläche ins Visier nehmen. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan