Register | Log in

squid3

Choose email to subscribe with

general

source: squid3 (main)
version: 3.5.23-5+deb9u1
maintainer: Luigi Gangitano (DMD)
uploaders: Santiago Garcia Mantinan [DMD]
arch: all any
std-ver: 3.9.8
VCS: Git (Browse)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 3.4.8-6+deb8u5
o-o-sec: 3.4.8-6+deb8u9
oldstable: 3.5.23-5+deb9u1
old-sec: 3.5.23-5+deb9u1

versioned links

3.4.8-6+deb8u5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.4.8-6+deb8u9: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.5.23-5+deb9u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

squid (17 bugs: 0, 12, 5, 0)
squid-cgi
squid-common
squid-dbg
squid-purge
squid3 (17 bugs: 0, 9, 8, 0)
squidclient

package is gone

This package is not in any development repository. This probably means that the package has been removed (or has been renamed). Thus the information here is of little interest ... the package is going to disappear unless someone takes it over and reintroduces it.

action needed

8 security issues in jessie high

There are 8 open security issues in jessie.

5 important issues:

CVE-2019-12528: An issue was discovered in Squid before 4.10. It allows a crafted FTP server to trigger disclosure of sensitive information from heap memory, such as information associated with other users' sessions or non-Squid processes.
CVE-2019-12523: An issue was discovered in Squid before 4.9. When handling a URN request, a corresponding HTTP request is made. This HTTP request doesn't go through the access checks that incoming HTTP requests go through. This causes all access checks to be bypassed and allows access to restricted HTTP servers, e.g., an attacker can connect to HTTP servers that only listen on localhost.
CVE-2019-18676: An issue was discovered in Squid 3.x and 4.x through 4.8. Due to incorrect input validation, there is a heap-based buffer overflow that can result in Denial of Service to all clients using the proxy. Severity is high due to this vulnerability occurring before normal security checks; any remote client that can reach the proxy port can trivially perform the attack via a crafted URI scheme.
CVE-2020-8450: An issue was discovered in Squid before 4.10. Due to incorrect buffer management, a remote client can cause a buffer overflow in a Squid instance acting as a reverse proxy.
CVE-2020-8449: An issue was discovered in Squid before 4.10. Due to incorrect input validation, it can interpret crafted HTTP requests in unexpected ways to access server resources prohibited by earlier security filters.

3 issues skipped by the security teams:

CVE-2016-2570: The Edge Side Includes (ESI) parser in Squid 3.x before 3.5.15 and 4.x before 4.0.7 does not check buffer limits during XML parsing, which allows remote HTTP servers to cause a denial of service (assertion failure and daemon exit) via a crafted XML document, related to esi/CustomParser.cc and esi/CustomParser.h.
CVE-2016-2569: Squid 3.x before 3.5.15 and 4.x before 4.0.7 does not properly append data to String objects, which allows remote servers to cause a denial of service (assertion failure and daemon exit) via a long string, as demonstrated by a crafted HTTP Vary header.
CVE-2016-3947: Heap-based buffer overflow in the Icmp6::Recv function in icmp/Icmp6.cc in the pinger utility in Squid before 3.5.16 and 4.x before 4.0.8 allows remote servers to cause a denial of service (performance degradation or transition failures) or write sensitive information to log files via an ICMPv6 packet.

Please fix them.

Created: 2016-02-26 Last update: 2020-02-08 18:32

13 security issues in stretch high

There are 13 open security issues in stretch.

12 important issues:

CVE-2019-12528: An issue was discovered in Squid before 4.10. It allows a crafted FTP server to trigger disclosure of sensitive information from heap memory, such as information associated with other users' sessions or non-Squid processes.
CVE-2019-12529: An issue was discovered in Squid 2.x through 2.7.STABLE9, 3.x through 3.5.28, and 4.x through 4.7. When Squid is configured to use Basic Authentication, the Proxy-Authorization header is parsed via uudecode. uudecode determines how many bytes will be decoded by iterating over the input and checking its table. The length is then used to start decoding the string. There are no checks to ensure that the length it calculates isn't greater than the input buffer. This leads to adjacent memory being decoded as well. An attacker would not be able to retrieve the decoded data unless the Squid maintainer had configured the display of usernames on error pages.
CVE-2019-12523: An issue was discovered in Squid before 4.9. When handling a URN request, a corresponding HTTP request is made. This HTTP request doesn't go through the access checks that incoming HTTP requests go through. This causes all access checks to be bypassed and allows access to restricted HTTP servers, e.g., an attacker can connect to HTTP servers that only listen on localhost.
CVE-2019-18676: An issue was discovered in Squid 3.x and 4.x through 4.8. Due to incorrect input validation, there is a heap-based buffer overflow that can result in Denial of Service to all clients using the proxy. Severity is high due to this vulnerability occurring before normal security checks; any remote client that can reach the proxy port can trivially perform the attack via a crafted URI scheme.
CVE-2019-18678: An issue was discovered in Squid 3.x and 4.x through 4.8. It allows attackers to smuggle HTTP requests through frontend software to a Squid instance that splits the HTTP Request pipeline differently. The resulting Response messages corrupt caches (between a client and Squid) with attacker-controlled content at arbitrary URLs. Effects are isolated to software between the attacker client and Squid. There are no effects on Squid itself, nor on any upstream servers. The issue is related to a request header containing whitespace between a header name and a colon.
CVE-2019-18679: An issue was discovered in Squid 2.x, 3.x, and 4.x through 4.8. Due to incorrect data management, it is vulnerable to information disclosure when processing HTTP Digest Authentication. Nonce tokens contain the raw byte value of a pointer that sits within heap memory allocation. This information reduces ASLR protections and may aid attackers isolating memory areas to target for remote code execution attacks.
CVE-2019-13345: The cachemgr.cgi web module of Squid through 4.7 has XSS via the user_name or auth parameter.
CVE-2019-18677: An issue was discovered in Squid 3.x and 4.x through 4.8 when the append_domain setting is used (because the appended characters do not properly interact with hostname length restrictions). Due to incorrect message processing, it can inappropriately redirect traffic to origins it should not be delivered to.
CVE-2019-12526: An issue was discovered in Squid before 4.9. URN response handling in Squid suffers from a heap-based buffer overflow. When receiving data from a remote server in response to an URN request, Squid fails to ensure that the response can fit within the buffer. This leads to attacker controlled data overflowing in the heap.
CVE-2020-8450: An issue was discovered in Squid before 4.10. Due to incorrect buffer management, a remote client can cause a buffer overflow in a Squid instance acting as a reverse proxy.
CVE-2020-8449: An issue was discovered in Squid before 4.10. Due to incorrect input validation, it can interpret crafted HTTP requests in unexpected ways to access server resources prohibited by earlier security filters.
CVE-2019-12525: An issue was discovered in Squid 3.3.9 through 3.5.28 and 4.x through 4.7. When Squid is configured to use Digest authentication, it parses the header Proxy-Authorization. It searches for certain tokens such as domain, uri, and qop. Squid checks if this token's value starts with a quote and ends with one. If so, it performs a memcpy of its length minus 2. Squid never checks whether the value is just a single quote (which would satisfy its requirements), leading to a memcpy of its length minus 1.

1 issue skipped by the security teams:

CVE-2018-19132: Squid before 4.4, when SNMP is enabled, allows a denial of service (Memory Leak) via an SNMP packet.

Please fix them.

Created: 2018-10-29 Last update: 2020-02-08 18:32

news

[2019-12-10] Accepted squid3 3.4.8-6+deb8u9 (source all amd64) into oldoldstable (Markus Koschany)
[2019-07-20] Accepted squid3 3.4.8-6+deb8u8 (source all amd64) into oldoldstable (Roberto C. Sanchez)
[2019-07-07] Accepted squid3 3.4.8-6+deb8u7 (source all amd64) into oldoldstable (Chris Lamb)
[2018-11-23] Accepted squid3 3.4.8-6+deb8u6 (source all amd64) into oldstable (Abhijith PA) (signed by: Markus Koschany)
[2018-10-08] Removed 3.5.27-1 from unstable (Debian FTP Masters)
[2018-10-08] Removed 3.5.23-5 from unstable (Debian FTP Masters)
[2018-09-02] squid3 REMOVED from testing (Debian testing watch)
[2018-02-23] Accepted squid3 3.4.8-6+deb8u5 (all source) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Salvatore Bonaccorso)
[2018-02-23] Accepted squid3 3.5.23-5+deb9u1 (source) into proposed-updates->stable-new, proposed-updates (Salvatore Bonaccorso)
[2018-02-22] Accepted squid3 3.5.23-5+deb9u1 (source) into stable->embargoed, stable (Salvatore Bonaccorso)
[2018-02-22] Accepted squid3 3.4.8-6+deb8u5 (all source) into oldstable->embargoed, oldstable (Salvatore Bonaccorso)
[2018-02-16] squid3 3.5.27-1 MIGRATED to testing (Debian testing watch)
[2018-02-13] Accepted squid3 3.5.27-1 (source amd64 all) into unstable (Luigi Gangitano)
[2018-02-02] Accepted squid3 3.1.20-2.2+deb7u8 (source all amd64) into oldoldstable (Roberto C. Sanchez)
[2017-06-10] squid3 3.5.23-5 MIGRATED to testing (Debian testing watch)
[2017-06-04] Accepted squid3 3.5.23-5 (source amd64 all) into unstable (Santiago Garcia Mantinan)
[2017-06-04] squid3 3.5.23-4 MIGRATED to testing (Debian testing watch)
[2017-06-02] Accepted squid3 3.5.23-4 (source amd64 all) into unstable (Santiago Garcia Mantinan)
[2017-04-14] squid3 3.5.23-3 MIGRATED to testing (Debian testing watch)
[2017-04-09] Accepted squid3 3.5.23-3 (source amd64 all) into unstable (Santiago Garcia Mantinan)
[2017-03-22] Accepted squid3 3.5.23-2 (source amd64 all) into unstable (Santiago Garcia Mantinan)
[2016-12-29] squid3 3.5.23-1 MIGRATED to testing (Debian testing watch)
[2016-12-25] Accepted squid3 3.1.20-2.2+deb7u7 (source all amd64) into oldstable (Markus Koschany)
[2016-12-24] Accepted squid3 3.4.8-6+deb8u4 (all source) into proposed-updates->stable-new, proposed-updates (Salvatore Bonaccorso)
[2016-12-19] Accepted squid3 3.5.23-1 (source amd64 all) into unstable (Luigi Gangitano)
[2016-11-04] squid3 3.5.22-1 MIGRATED to testing (Debian testing watch)
[2016-10-29] Accepted squid3 3.5.22-1 (source amd64 all) into unstable (Luigi Gangitano)
[2016-07-24] Accepted squid3 3.4.8-6+deb8u3 (source all amd64) into proposed-updates->stable-new, proposed-updates (Santiago Ruano Rincón)
[2016-07-22] Accepted squid3 3.1.20-2.2+deb7u6 (source all amd64) into oldstable (Santiago Ruano Rincón)
[2016-05-16] Accepted squid3 3.1.20-2.2+deb7u5 (source all amd64) into oldstable (signed by: Santiago Ruano Rincón)

1
2

bugs [bug history graph]

all: 0

links

homepage
buildd: logs, clang, cross
popcon
browse source code
edit tags
security tracker
screenshots

Debian Package Tracker — Copyright 2013-2018 The Distro Tracker Developers

Report problems to the tracker.debian.org pseudo-package in the Debian BTS.

Documentation — Bugs — Git Repository — Contributing