Bug 1962599 (CVE-2021-31808) - CVE-2021-31808 squid: integer overflow in HTTP Range header
Summary: CVE-2021-31808 squid: integer overflow in HTTP Range header
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2021-31808
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1962600 1963389 1963390
Blocks: 1959539
TreeView+ depends on / blocked
 
Reported: 2021-05-20 10:44 UTC by Marian Rehak
Modified: 2022-04-17 21:24 UTC (History)
7 users (show)

Fixed In Version: squid 4.15, squid 5.0.6
Doc Type: If docs needed, set a value
Doc Text:
An integer overflow flaw was found in Squid, where it is vulnerable to a denial of service attack against all clients using the proxy. The highest threat from this vulnerability is to system availability.
Clone Of:
Environment:
Last Closed: 2021-11-09 19:21:37 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4292 0 None Waiting on Red Hat [rfe] RFE for BGP functionality for Lumen 2022-06-13 15:13:55 UTC

Description Marian Rehak 2021-05-20 10:44:23 UTC
Due to an integer overflow bug Squid is vulnerable to a Denial of Service attack against all clients using the proxy.

External Reference:

https://github.com/squid-cache/squid/security/advisories/GHSA-pxwq-f3qr-w2xf

Comment 1 Marian Rehak 2021-05-20 10:46:04 UTC
Created squid tracking bugs for this issue:

Affects: fedora-all [bug 1962600]

Comment 5 errata-xmlrpc 2021-11-09 18:06:07 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 6 Product Security DevOps Team 2021-11-09 19:21:35 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2021-31808


Note You need to log in before you can comment on or make changes to this bug.