Bug 1221139 (CVE-2024-25111) - VUL-0: CVE-2024-25111: squid,squid3: denial of service in HTTP chunked decoding
Summary: VUL-0: CVE-2024-25111: squid,squid3: denial of service in HTTP chunked decoding
Status: RESOLVED DUPLICATE of bug 1216715
Alias: CVE-2024-25111
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Major
Target Milestone: ---
Assignee: Adam Majer
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/396517/
Whiteboard: CVSSv3.1:SUSE:CVE-2024-25111:7.5:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-07 17:03 UTC by SMASH SMASH
Modified: 2024-03-08 08:58 UTC (History)
1 user (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-03-07 17:03:25 UTC 
Squid is a web proxy cache. Starting in version 3.5.27 and prior to version 6.8, Squid may be vulnerable to a Denial of Service attack against HTTP Chunked decoder due to an uncontrolled recursion bug. This problem allows a remote attacker to cause Denial of Service when sending a crafted, chunked, encoded HTTP Message. This bug is fixed in Squid version 6.8. In addition, patches addressing this problem for the stable releases can be found in Squid's patch archives. There is no workaround for this issue.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25111
https://www.cve.org/CVERecord?id=CVE-2024-25111
https://github.com/squid-cache/squid/security/advisories/GHSA-72c2-c3wm-8qxc
https://bugzilla.redhat.com/show_bug.cgi?id=2268366

Patch:
http://www.squid-cache.org/Versions/v6/SQUID-2024_1.patch
Comment 1 Adam Majer 2024-03-08 08:55:15 UTC 
Duplicate of Bug 1216715 ?
Comment 2 Andrea Mattiazzo 2024-03-08 08:58:38 UTC 
Yes, will close this. Thanks.

*** This bug has been marked as a duplicate of bug 1216715 ***