The version of squid installed on the remote host is prior to 4.15-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2SQUID4-2023-004 advisory.

    Squid through 4.14 and 5.x through 5.0.5, in some configurations, allows information disclosure because of     an out-of-bounds read in WCCP protocol data. This can be leveraged as part of a chain for remote code     execution as nobody. (CVE-2021-28116)

    An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. Due to a buffer-management bug, it     allows a denial of service. When resolving a request with the urn: scheme, the parser leaks a small amount     of memory. However, there is an unspecified attack methodology that can easily trigger a large amount of     memory consumption. (CVE-2021-28651)

    An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. Due to incorrect parser validation, it     allows a Denial of Service attack against the Cache Manager API. This allows a trusted client to trigger     memory leaks that. over time, lead to a Denial of Service via an unspecified short query string. This     attack is limited to clients with Cache Manager API access privilege. (CVE-2021-28652)

    An issue was discovered in Squid 4.x before 4.15 and 5.x before 5.0.6. If a remote server sends a certain     response header over HTTP or HTTPS, there is a denial of service. This header can plausibly occur in     benign network traffic. (CVE-2021-28662)

    An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. Due to a memory-management bug, it is     vulnerable to a Denial of Service attack (against all clients using the proxy) via HTTP Range request     processing. (CVE-2021-31806)

    An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. An integer overflow problem allows a     remote server to achieve Denial of Service when delivering responses to HTTP Range requests. The issue     trigger is a header that can be expected to exist in HTTP traffic without any malicious intent.
    (CVE-2021-31807)

    An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. Due to an input-validation bug, it is     vulnerable to a Denial of Service attack (against all clients using the proxy). A client sends an HTTP     Range request to trigger this. (CVE-2021-31808)

    Squid before 4.15 and 5.x before 5.0.6 allows remote servers to cause a denial of service (affecting     availability to all clients) via an HTTP response. The issue trigger is a header that can be expected to     exist in HTTP traffic without any malicious intent by the server. (CVE-2021-33620)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Ubuntu 18.04 LTS / 20.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-4981-1 advisory.

    Joshua Rogers discovered that Squid incorrectly handled requests with the urn: scheme. A remote attacker     could possibly use this issue to cause Squid 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. This issue was only addressed in Ubuntu 20.04 LTS, Ubuntu 20.10, and Ubuntu 21.04.
    (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. This issue was only     affected Ubuntu 20.04 LTS, Ubuntu 20.10, and Ubuntu 21.04. (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)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Several vulnerabilities were discovered in Squid, a proxy caching server. 

CVE-2021-28651

Due to a buffer-management bug, it allows a denial of service. When resolving a request with the urn: scheme, the parser leaks a small amount of memory. However, there is an unspecified attack methodology that can easily trigger a large amount of memory consumption.

CVE-2021-28652

Due to incorrect parser validation, it allows a Denial of Service attack against the Cache Manager API. This allows a trusted client to trigger memory leaks that. over time, lead to a Denial of Service via an unspecified short query string. This attack is limited to clients with Cache Manager API access privilege.

CVE-2021-31806

Due to a memory-management bug, it is vulnerable to a Denial of Service attack (against all clients using the proxy) via HTTP Range request processing.

CVE-2021-31807

An integer overflow problem allows a remote server to achieve Denial of Service when delivering responses to HTTP Range requests. The issue trigger is a header that can be expected to exist in HTTP traffic without any malicious intent.

CVE-2021-31808

Due to an input-validation bug, it is vulnerable to a Denial of Service attack (against all clients using the proxy). A client sends an HTTP Range request to trigger this.

CVE-2021-33620

Remote servers to cause a denial of service (affecting availability to all clients) via an HTTP response. The issue trigger is a header that can be expected to exist in HTTP traffic without any malicious intent by the server.

For Debian 9 stretch, these problems have been fixed in version 3.5.23-5+deb9u7.

We recommend that you upgrade your squid3 packages.

For the detailed security status of squid3 please refer to its security tracker page at:
https://security-tracker.debian.org/tracker/squid3

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to the versions of the squid packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - An issue was discovered in Squid before 4.12 and 5.x     before 5.0.3. Due to use of a potentially dangerous     function, Squid and the default certificate validation     helper are vulnerable to a Denial of Service when     opening a TLS connection to an attacker-controlled     server for HTTPS. This occurs because unrecognized     error values are mapped to NULL, but later code expects     that each error value is mapped to a valid error     string.(CVE-2020-14058)

  - 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)

  - An issue was discovered in Squid before 4.15 and 5.x     before 5.0.6. Due to an input-validation bug, it is     vulnerable to a Denial of Service attack (against all     clients using the proxy). A client sends an HTTP Range     request to trigger this.(CVE-2021-31808)

  - An issue was discovered in Squid before 4.15 and 5.x     before 5.0.6. Due to a buffer-management bug, it allows     a denial of service. When resolving a request with the     urn: scheme, the parser leaks a small amount of memory.
    However, there is an unspecified attack methodology     that can easily trigger a large amount of memory     consumption.(CVE-2021-28651)

  - An issue was discovered in Squid before 4.15 and 5.x     before 5.0.6. Due to a memory-management bug, it is     vulnerable to a Denial of Service attack (against all     clients using the proxy) via HTTP Range request     processing.(CVE-2021-31806)

  - Squid before 4.15 and 5.x before 5.0.6 allows remote     servers to cause a denial of service (affecting     availability to all clients) via an HTTP response. The     issue trigger is a header that can be expected to exist     in HTTP traffic without any malicious intent by the     server.(CVE-2021-33620)

  - An issue was discovered in Squid before 4.15 and 5.x     before 5.0.6. An integer overflow problem allows a     remote server to achieve Denial of Service when     delivering responses to HTTP Range requests. The issue     trigger is a header that can be expected to exist in     HTTP traffic without any malicious     intent.(CVE-2021-31807)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Published	Updated	Severity
181987	Amazon Linux 2 : squid (ALASSQUID4-2023-004)	Nessus	Amazon Linux Local Security Checks	9/27/2023	12/11/2024	medium
150232	Ubuntu 18.04 LTS / 20.04 LTS : Squid vulnerabilities (USN-4981-1)	Nessus	Ubuntu Local Security Checks	6/3/2021	8/27/2024	high
150796	Debian DLA-2685-1 : squid3 security update	Nessus	Debian Local Security Checks	6/15/2021	12/21/2023	high
153296	EulerOS 2.0 SP2 : squid (EulerOS-SA-2021-2433)	Nessus	Huawei Local Security Checks	9/14/2021	11/30/2023	high

Detections

Analytics

Plugins Search

medium

high

high

high