Bug 1770375 (CVE-2019-18676) - CVE-2019-18676 squid: Buffer overflow in URI processor
Summary: CVE-2019-18676 squid: Buffer overflow in URI processor
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-18676
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: 1770376 1771271 1771272
Blocks: 1770377
TreeView+ depends on / blocked
 
Reported: 2019-11-08 20:05 UTC by Pedro Sampaio
Modified: 2021-02-16 21:05 UTC (History)
6 users (show)

Fixed In Version: squid 4.9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:23:08 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4743 0 None None None 2020-11-04 03:31:45 UTC

Description Pedro Sampaio 2019-11-08 20:05:07 UTC
Due to incorrect input validation Squid is vulnerable to a buffer overflow which can result in Denial of Service to all clients using the proxy.

References:

http://www.squid-cache.org/Advisories/SQUID-2019_8.txt

Comment 1 Pedro Sampaio 2019-11-08 20:05:21 UTC
Created squid tracking bugs for this issue:

Affects: fedora-all [bug 1770376]

Comment 3 Huzaifa S. Sidhpurwala 2019-11-12 05:27:24 UTC
External References:

http://www.squid-cache.org/Advisories/SQUID-2019_8.txt

Comment 5 Serhii Zashchelkin 2020-01-22 14:26:06 UTC
Hi

Could anyone please clarify, whether a patch for Squid V3 will be released for this issue?

Thanks,
Serhii

Comment 6 Product Security DevOps Team 2020-11-04 02:23:08 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-2019-18676

Comment 7 errata-xmlrpc 2020-11-04 03:31:26 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2020:4743 https://access.redhat.com/errata/RHSA-2020:4743


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