Search vulnerabilities

Results 112

Export CSV
CVE-2020-8450

squid: Buffer overflow in reverse-proxy configurations

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.

CVSS 3.1 · 7.3 High EPSS 71.8% KEV · Not listed
Vendors
Products
CVE-2020-8449

squid: Improper input validation issues in HTTP Request processing

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.

CVSS 3.1 · 7.5 High EPSS 8.3% KEV · Not listed
Vendors
Products
CVE-2020-25097

squid: improper input validation may allow a trusted client to perform HTTP request smuggling

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.

CVSS 3.1 · 8.6 High EPSS 7.3% KEV · Not listed
Vendors
Products
CVE-2020-24606

squid: Improper input validation could result in a DoS

Squid before 4.13 and 5.x before 5.0.4 allows a trusted peer to perform Denial of Service by consuming all available CPU cycles during handling of a crafted Cache Digest response message. This only occurs when cache_peer is used with the cache digests feature. The problem exists because peerDigestHandleReply() livelocking in peer_digest.cc mishandles EOF.

CVSS 3.1 · 8.6 High EPSS 4.6% KEV · Not listed
Vendors
Products
CVE-2020-15811

squid: HTTP Request Splitting could result in cache poisoning

An issue was discovered in Squid before 4.13 and 5.x before 5.0.4. Due to incorrect data validation, HTTP Request Splitting attacks may succeed against HTTP and HTTPS traffic. This leads to cache poisoning. This allows any client, including browser scripts, to bypass local security and poison the browser cache and any downstream caches with content from an arbitrary source. Squid uses a string search instead of parsing the Transfer-Encoding header to find chunked encoding. This allows an attacker to hide a second request inside Transfer-Encoding: it is interpreted by Squid as chunked and split out into a second request delivered upstream. Squid will then deliver two distinct responses to the client, corrupting any downstream caches.

CVSS 3.1 · 6.5 Medium EPSS 3.8% KEV · Not listed
Vendors
Products
CVE-2020-15810

squid: HTTP Request Smuggling could result in cache poisoning

An issue was discovered in Squid before 4.13 and 5.x before 5.0.4. Due to incorrect data validation, HTTP Request Smuggling attacks may succeed against HTTP and HTTPS traffic. This leads to cache poisoning. This allows any client, including browser scripts, to bypass local security and poison the proxy cache and any downstream caches with content from an arbitrary source. When configured for relaxed header parsing (the default), Squid relays headers containing whitespace characters to upstream servers. When this occurs as a prefix to a Content-Length header, the frame length specified will be ignored by Squid (allowing for a conflicting length to be used from another Content-Length header) but relayed upstream.

CVSS 3.1 · 6.5 Medium EPSS 2.3% KEV · Not listed
Vendors
Products
CVE-2020-15049

squid: Request smuggling and poisoning attack against the HTTP cache

An issue was discovered in http/ContentLengthInterpreter.cc in Squid before 4.12 and 5.x before 5.0.3. A Request Smuggling and Poisoning attack can succeed against the HTTP cache. The client sends an HTTP request with a Content-Length header containing "+\ "-" or an uncommon shell whitespace character prefix to the length field-value.

CVSS 3.1 · 9.9 Critical EPSS 5.3% KEV · Not listed
CVE-2020-14059

squid: DoS when processing objects in an SMP cache due to an incorrect synchronization

An issue was discovered in Squid 5.x before 5.0.3. Due to an Incorrect Synchronization, a Denial of Service can occur when processing objects in an SMP cache because of an Ipc::Mem::PageStack::pop ABA problem during access to the memory page/slot management list.

CVSS 3.1 · 6.5 Medium EPSS 4.4% KEV · Not listed
Vendors
Products
CVE-2020-14058

squid: DoS in TLS handshake

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.

CVSS 3.1 · 7.5 High EPSS 2.5% KEV · Not listed
Vendors
Products
CVE-2020-11945

squid: improper access restriction upon Digest Authentication nonce replay could lead to remote code execution

An issue was discovered in Squid before 5.0.2. A remote attacker can replay a sniffed Digest Authentication nonce to gain access to resources that are otherwise forbidden. This occurs because the attacker can overflow the nonce reference counter (a short integer). Remote code execution may occur if the pooled token credentials are freed (instead of replayed as valid credentials).

CVSS 3.1 · 9.8 Critical EPSS 27.2% KEV · Not listed
Vendors
Products
CVE-2019-18679

squid: Information Disclosure issue in HTTP Digest Authentication

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.

CVSS 3.1 · 7.5 High EPSS 43.1% KEV · Not listed
Vendors
Products
CVE-2019-18678

squid: HTTP Request Splitting issue in HTTP message processing

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.

CVSS 3.1 · 5.3 Medium EPSS 6.2% KEV · Not listed
Vendors
Products
CVE-2019-18677

squid: Cross-Site Request Forgery issue in HTTP Request processing

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.

CVSS 3.1 · 6.1 Medium EPSS 3.9% KEV · Not listed
Vendors
Products
CVE-2019-18676

squid: Buffer overflow in URI processor

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.

CVSS 3.1 · 7.5 High EPSS 9.2% KEV · Not listed
Vendors
Products
CVE-2019-12854

squid: Denial of service in cachemgr.cgi

Due to incorrect string termination, Squid cachemgr.cgi 4.0 through 4.7 may access unallocated memory. On systems with memory access protections, this can cause the CGI process to terminate unexpectedly, resulting in a denial of service for all clients using it.

CVSS 3.1 · 7.5 High EPSS 11.7% KEV · Not listed
Vendors
Products
CVE-2019-12529

squid: Out of bounds read in Proxy-Authorization header causes DoS

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.

CVSS 3.1 · 5.9 Medium EPSS 7.8% KEV · Not listed
Vendors
Products
CVE-2019-12528

squid: Information Disclosure issue in FTP Gateway

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.

CVSS 3.1 · 7.5 High EPSS 10.5% KEV · Not listed
Vendors
Products
CVE-2019-12527

squid: heap-based buffer overflow in HttpHeader::getAuth

An issue was discovered in Squid 4.0.23 through 4.7. When checking Basic Authentication with HttpHeader::getAuth, Squid uses a global buffer to store the decoded data. Squid does not check that the decoded length isn't greater than the buffer, leading to a heap-based buffer overflow with user controlled data.

CVSS 3.1 · 8.8 High EPSS 50.3% KEV · Not listed
Vendors
Products
CVE-2019-12526

squid: Heap overflow issue in URN processing

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.

CVSS 3.1 · 9.8 Critical EPSS 20.3% KEV · Not listed
Vendors
Products