CVE-2020-25097

Squid is a high-performance proxy caching server. It handles all requests in a single, non-blocking, I/O-driven process and keeps meta data and implements negative caching of failed requests.

Security Fix(es):

An issue was discovered in Squid through 4.13 and 5.x through 5.0.4. Due to improper input validation, it allows a trusted client to perform HTTP Request Smuggling and access services otherwise forbidden by the security controls. This occurs for certain uri_whitespace configuration settings.(CVE-2020-25097)

Squid is a high-performance proxy caching server for web clients, supporting FTP, Gopher, and HTTP data objects.

Security Fix(es):

• squid: improper input validation may allow a trusted client to perform HTTP request smuggling (CVE-2020-25097)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

An issue was discovered in Squid through 4.13 and 5.x through 5.0.4. Due to improper input validation, it allows a trusted client to perform HTTP Request Smuggling and access services otherwise forbidden by the security controls. This occurs for certain uri_whitespace configuration settings.

Squid is a high-performance proxy caching server for web clients, supporting FTP, Gopher, and HTTP data objects.

Security Fix(es):

• squid: improper input validation may allow a trusted client to perform HTTP request smuggling (CVE-2020-25097)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

• CVE-2020-15049: fix incorrect validation of Content-Length field leading to Http smuggling and Poisoning attack
• CVE-2020-14058: fix handling of unknown SSL errors which resulted in denial of service
• CVE-2020-25097: fix improper input validation allowing HTTP smuggling from trusted client
• CVE-2020-11945: fix nonce reference counter overflow allowing replay attack
• CVE-2020-24606: fix handle of EOF in peerDigestHandleReply() leading to Denial of service
• CVE-2020-8517: fix incorrect input validation allowing writing outside of buffer and leading to denial of service
• CVE-2020-8449: fix improper HTTP request validation allowing access to resources which are prohibited by security filters
• CVE-2020-8450: fix incorrect buffer managment leading to buffer overflow
• CVE-2021-28651: fix memory leak leading to denial of service

• CVE-2020-15049: fix incorrect validation of Content-Length field leading to Http smuggling and Poisoning attack
• CVE-2020-14058: fix handling of unknown SSL errors which resulted in denial of service
• CVE-2020-25097: fix improper input validation allowing HTTP smuggling from trusted client
• CVE-2020-11945: fix nonce reference counter overflow allowing replay attack
• CVE-2020-24606: fix handle of EOF in peerDigestHandleReply() leading to Denial of service
• CVE-2020-8517: fix incorrect input validation allowing writing outside of buffer and leading to denial of service
• CVE-2020-8449: fix improper HTTP request validation allowing access to resources which are prohibited by security filters
• CVE-2020-8450: fix incorrect buffer managment leading to buffer overflow
• CVE-2021-28651: fix memory leak leading to denial of service

Updated squid packages fix security vulnerabilities:

Due to improper input validation Squid is vulnerable to an HTTP Request Smuggling attack. This problem allows a trusted client to perform HTTP Request Smuggling and access services otherwise forbidden by Squid security controls (CVE-2020-25097).

Joshua Rogers discovered that Squid incorrectly handled requests with the urn: scheme. A remote attacker could possibly use this issue to causeSquid to consume resources, leading to a denial of service (CVE-2021-28651).

Joshua Rogers discovered that Squid incorrectly handled requests to the Cache Manager API. A remote attacker with access privileges could possibly use this issue to cause Squid to consume resources, leading to a denial of service (CVE-2021-28652).

Joshua Rogers discovered that Squid incorrectly handled certain response headers. A remote attacker could possibly use this issue to cause Squid to crash, resulting in a denial of service (CVE-2021-28662).

Joshua Rogers discovered that Squid incorrectly handled range request processing. A remote attacker could possibly use this issue to cause Squid to crash, resulting in a denial of service (CVE-2021-31806, CVE-2021-31807, CVE-2021-31808).

Joshua Rogers discovered that Squid incorrectly handled certain HTTP responses. A remote attacker could possibly use this issue to cause Squid to crash, resulting in a denial of service (CVE-2021-33620).

The squid package has been updated to version 4.15, fixing theese issues and other bugs.

This update for squid fixes the following issues:

• update to 4.15:
• CVE-2021-28652: Broken cache manager URL parsing (bsc#1185918)
• CVE-2021-28651: Memory leak in RFC 2169 response parsing (bsc#1185921)
• CVE-2021-28662: Limit HeaderLookupTable_t::lookup() to BadHdr and specific IDs (bsc#1185919)
• CVE-2021-31806: Handle more Range requests (bsc#1185916)
• CVE-2020-25097: HTTP Request Smuggling vulnerability (bsc#1183436)
• Handle more partial responses (bsc#1185923)
• fix previous change to reinstante permissions macros, because the wrong path has been used (bsc#1171569).
• use libexecdir instead of libdir to conform to recent changes in Factory (bsc#1171164).
• Reinstate permissions macros for pinger binary, because the permissions package is also responsible for setting up the cap_net_raw capability, currently a fresh squid install doesn't get a capability bit at all (bsc#1171569).
• Change pinger and basic_pam_auth helper to use standard permissions. pinger uses cap_net_raw=ep instead (bsc#1171569)

This update was imported from the SUSE:SLE-15:Update update project.

This update for squid fixes the following issues:

• update to 4.15:
• CVE-2021-28652: Broken cache manager URL parsing (bsc#1185918)
• CVE-2021-28651: Memory leak in RFC 2169 response parsing (bsc#1185921)
• CVE-2021-28662: Limit HeaderLookupTable_t::lookup() to BadHdr and specific IDs (bsc#1185919)
• CVE-2021-31806: Handle more Range requests (bsc#1185916)
• CVE-2020-25097: HTTP Request Smuggling vulnerability (bsc#1183436)
• Handle more partial responses (bsc#1185923)
• fix previous change to reinstante permissions macros, because the wrong path has been used (bsc#1171569).
• use libexecdir instead of libdir to conform to recent changes in Factory (bsc#1171164).
• Reinstate permissions macros for pinger binary, because the permissions package is also responsible for setting up the cap_net_raw capability, currently a fresh squid install doesn't get a capability bit at all (bsc#1171569).
• Change pinger and basic_pam_auth helper to use standard permissions. pinger uses cap_net_raw=ep instead (bsc#1171569)

These are all security issues fixed in the squid-4.16-1.5 package on the GA media of openSUSE Tumbleweed.

This update for squid fixes the following issues:

• update to 4.15:
• CVE-2021-28652: Broken cache manager URL parsing (bsc#1185918)
• CVE-2021-28651: Memory leak in RFC 2169 response parsing (bsc#1185921)
• CVE-2021-28662: Limit HeaderLookupTable_t::lookup() to BadHdr and specific IDs (bsc#1185919)
• CVE-2021-31806: Handle more Range requests (bsc#1185916)
• CVE-2020-25097: HTTP Request Smuggling vulnerability (bsc#1183436)
• Handle more partial responses (bsc#1185923)
• fix previous change to reinstante permissions macros, because the wrong path has been used (bsc#1171569).
• use libexecdir instead of libdir to conform to recent changes in Factory (bsc#1171164).
• Reinstate permissions macros for pinger binary, because the permissions package is also responsible for setting up the cap_net_raw capability, currently a fresh squid install doesn't get a capability bit at all (bsc#1171569).
• Change pinger and basic_pam_auth helper to use standard permissions. pinger uses cap_net_raw=ep instead (bsc#1171569)

This update for squid fixes the following issues:

• update to 4.15:
• CVE-2021-28652: Broken cache manager URL parsing (bsc#1185918)
• CVE-2021-28651: Memory leak in RFC 2169 response parsing (bsc#1185921)
• CVE-2021-28662: Limit HeaderLookupTable_t::lookup() to BadHdr and specific IDs (bsc#1185919)
• CVE-2021-31806: Handle more Range requests (bsc#1185916)
• CVE-2020-25097: HTTP Request Smuggling vulnerability (bsc#1183436)
• Handle more partial responses (bsc#1185923)
• fix previous change to reinstante permissions macros, because the wrong path has been used (bsc#1171569).
• use libexecdir instead of libdir to conform to recent changes in Factory (bsc#1171164).
• Reinstate permissions macros for pinger binary, because the permissions package is also responsible for setting up the cap_net_raw capability, currently a fresh squid install doesn't get a capability bit at all (bsc#1171569).
• Change pinger and basic_pam_auth helper to use standard permissions. pinger uses cap_net_raw=ep instead (bsc#1171569)

This update for squid3 fixes the following issues:

• CVE-2021-28651: Fixed a denial of service issue when processing URN resource identifiers (bsc#1185921).
• CVE-2020-25097: Fixed an HTTP request smuggling issue (bsc#1183436).

This update for squid fixes the following issues:

• CVE-2020-25097: Fixed HTTP Request Smuggling (bsc#1183436)
• CVE-2021-28651: Fixed DoS in URN processing (bsc#1185921)
• CVE-2021-46784: Fixed DoS when processing gopher server responses (bsc#1200907)

Alex Rousskov and Amit Klein discovered that Squid incorrectly handled certain Content-Length headers. A remote attacker could possibly use this issue to perform an HTTP request smuggling attack, resulting in cache poisoning. This issue only affected Ubuntu 20.04 LTS. (CVE-2020-15049)

Jianjun Chen discovered that Squid incorrectly validated certain input. A remote attacker could use this issue to perform HTTP Request Smuggling and possibly access services forbidden by the security controls. (CVE-2020-25097)