A flaw was found in Squid. The limits applied for validation of HTTP response headers are applied before caching. However, Squid may grow a cached HTTP response header beyond the configured maximum size, causing a stall or crash of the worker process when a large header is retrieved from the disk cache, resulting in a denial of service.
Workaround:
The product does not handle or incorrectly handles an exceptional condition.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2023:7465 | vendor advisory |
https://access.redhat.com/errata/RHSA-2023:7668 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:0072 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:0397 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:0771 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:0772 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:0773 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:1153 | vendor advisory |
https://access.redhat.com/security/cve/CVE-2023-5824 | third party advisory vdb entry |
https://bugzilla.redhat.com/show_bug.cgi?id=2245914 | issue tracking |
https://github.com/squid-cache/squid/security/advisories/GHSA-543m-w2m2-g255 | vendor advisory |
https://security.netapp.com/advisory/ntap-20231130-0003/ |