Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1536939 - (CVE-2018-1000024) CVE-2018-1000024 squid: Incorrect pointer handling when processing ESI Responses can lead to denial of service
CVE-2018-1000024 squid: Incorrect pointer handling when processing ESI Respon...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180119,repor...
: Security
Depends On: 1582301 1536940
Blocks: 1536944
  Show dependency treegraph
 
Reported: 2018-01-22 00:19 EST by Sam Fowler
Modified: 2018-10-18 03:35 EDT (History)
5 users (show)

See Also:
Fixed In Version: squid 3.5.27, squid 4.0.23
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-01-22 00:19:02 EST
Due to incorrect pointer handling, Squid versions 3.x (prior to 3.5.27) and 4.x (prior to 4.0.23) are vulnerable to a denial of service attack when processing ESI responses. This problem allows a remote server delivering certain ESI response syntax to trigger a denial of service for all clients accessing the Squid service. 

Upstream Advisory:
http://www.squid-cache.org/Advisories/SQUID-2018_1.txt

Upstream Patches:
http://www.squid-cache.org/Versions/v3/3.5/changesets/SQUID-2018_1.patch
http://www.squid-cache.org/Versions/v4/changesets/SQUID-2018_1.patch
Comment 1 Sam Fowler 2018-01-22 00:19:36 EST
Created squid tracking bugs for this issue:

Affects: fedora-all [bug 1536940]
Comment 3 Stefan Cornelius 2018-05-24 07:24:23 EDT
Mitigation:

A workaround for this issue is to not use the internal ESI parser, which can be achieved by adding either the "esi_parser expat" or "esi_parser libxml2" configuration directive to the squid configuration file (for example /etc/squid/squid.conf).

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