Bug 1959537 (CVE-2021-33620)

Summary: CVE-2021-33620 squid: denial of service in HTTP response processing
Product: [Other] Security Response Reporter: Guilherme de Almeida Suckevicz <gsuckevi>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: anon.amish, code, icesalov, jonathansteffan, luhliari, mcascell
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: squid 4.15, squid 5.0.6 Doc Type: If docs needed, set a value
Doc Text:
An input validation flaw was found in Squid. This issue could allow a remote server to perform a denial of service against all clients using the proxy when delivering HTTP response messages. The highest threat from this vulnerability is to system availability.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-09 18:54:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1959538, 1960215, 1960216    
Bug Blocks: 1959539    

Description Guilherme de Almeida Suckevicz 2021-05-11 18:04:54 UTC
Due to an input validation bug Squid is vulnerable to a Denial of Service against all clients using the proxy. This problem allows a remote server to perform Denial of Service when delivering HTTP Response messages. The issue trigger is a header which can be expected to exist in HTTP traffic without any malicious intent by the server.


Comment 1 Guilherme de Almeida Suckevicz 2021-05-11 18:05:11 UTC
Created squid tracking bugs for this issue:

Affects: fedora-all [bug 1959538]

Comment 10 errata-xmlrpc 2021-11-09 18:05:41 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2021:4292 https://access.redhat.com/errata/RHSA-2021:4292

Comment 11 Product Security DevOps Team 2021-11-09 18:54:41 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):