https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 10:05:59 +0000 https://cve.radiocsirt.org/vuln/alsa-2020:4743 <p><strong>Affected:</strong> AlmaLinux:8: libecap, AlmaLinux:8: libecap-devel</p> <p>Squid is a high-performance proxy caching server for web clients, supporting FTP, Gopher, and HTTP data objects.</p> <p>The following packages have been upgraded to a later upstream version: squid (4.11). (BZ#1829467)</p> <p>Security Fix(es):</p> <p>* squid: Improper input validation in request allows for proxy manipulation (CVE-2019-12520)</p> <p>* squid: Off-by-one error in addStackElement allows for heap buffer overflow and crash (CVE-2019-12521)</p> <p>* squid: Improper input validation in URI processor (CVE-2019-12523)</p> <p>* squid: Improper access restriction in url_regex may lead to security bypass (CVE-2019-12524)</p> <p>* squid: Heap overflow issue in URN processing (CVE-2019-12526)</p> <p>* squid: Information Disclosure issue in FTP Gateway (CVE-2019-12528)</p> <p>* squid: Out of bounds read in Proxy-Authorization header causes DoS (CVE-2019-12529)</p> <p>* squid: Denial of service in cachemgr.cgi (CVE-2019-12854)</p> <p>* squid: Buffer overflow in URI processor (CVE-2019-18676)</p> <p>* squid: Cross-Site Request Forgery issue in HTTP Request processing (CVE-2019-18677)</p> <p>* squid: HTTP Request Splitting issue in HTTP message processing (CVE-2019-18678)</p> <p>* squid: Information Disclosure issue in HTTP Digest Authentication (CVE-2019-18679)</p> <p>* squid: Mishandled HTML in the host parameter to cachemgr.cgi results in insecure behaviour (CVE-2019-18860)</p> <p>* squid: Improper input validation issues in HTTP Request processing (CVE-2020-8449)</p> <p>* squid: Buffer overflow in reverse-proxy configurations (CVE-2020-8450)</p> <p>* squid: DoS in TLS handshake (…</p> <p><strong>Affected:</strong> AlmaLinux:8: libecap, AlmaLinux:8: libecap-devel</p> <p>Squid is a high-performance proxy caching server for web clients, supporting FTP, Gopher, and HTTP data objects.</p> <p>The following packages have been upgraded to a later upstream version: squid (4.11). (BZ#1829467)</p> <p>Security Fix(es):</p> <p>* squid: Improper input validation in request allows for proxy manipulation (CVE-2019-12520)</p> <p>* squid: Off-by-one error in addStackElement allows for heap buffer overflow and crash (CVE-2019-12521)</p> <p>* squid: Improper input validation in URI processor (CVE-2019-12523)</p> <p>* squid: Improper access restriction in url_regex may lead to security bypass (CVE-2019-12524)</p> <p>* squid: Heap overflow issue in URN processing (CVE-2019-12526)</p> <p>* squid: Information Disclosure issue in FTP Gateway (CVE-2019-12528)</p> <p>* squid: Out of bounds read in Proxy-Authorization header causes DoS (CVE-2019-12529)</p> <p>* squid: Denial of service in cachemgr.cgi (CVE-2019-12854)</p> <p>* squid: Buffer overflow in URI processor (CVE-2019-18676)</p> <p>* squid: Cross-Site Request Forgery issue in HTTP Request processing (CVE-2019-18677)</p> <p>* squid: HTTP Request Splitting issue in HTTP message processing (CVE-2019-18678)</p> <p>* squid: Information Disclosure issue in HTTP Digest Authentication (CVE-2019-18679)</p> <p>* squid: Mishandled HTML in the host parameter to cachemgr.cgi results in insecure behaviour (CVE-2019-18860)</p> <p>* squid: Improper input validation issues in HTTP Request processing (CVE-2020-8449)</p> <p>* squid: Buffer overflow in reverse-proxy configurations (CVE-2020-8450)</p> <p>* squid: DoS in TLS handshake (…</p> https://cve.radiocsirt.org/vuln/alsa-2020:4743 https://cve.radiocsirt.org/vuln/bdu:2021-01748 bdu:2021-01748 https://cve.radiocsirt.org/vuln/bdu:2021-01748 https://cve.radiocsirt.org/vuln/certfr-2019-avi-552 certfr-2019-avi-552 https://cve.radiocsirt.org/vuln/certfr-2019-avi-552 https://cve.radiocsirt.org/vuln/euvd-2026-58845 EUVD-2026-58845 https://cve.radiocsirt.org/vuln/euvd-2026-58845 https://cve.radiocsirt.org/vuln/fkie_cve-2019-18678 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2019-18678 https://cve.radiocsirt.org/vuln/ghsa-jvgf-c7c2-w98p <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-jvgf-c7c2-w98p https://cve.radiocsirt.org/vuln/gsd-2019-18678 gsd-2019-18678 https://cve.radiocsirt.org/vuln/gsd-2019-18678 https://cve.radiocsirt.org/vuln/opensuse-su-2019:2540-1 <p>Security update for squid</p> <p>Security update for squid</p> https://cve.radiocsirt.org/vuln/opensuse-su-2019:2540-1 https://cve.radiocsirt.org/vuln/suse-su-2019:2975-1 <p>Security update for squid</p> <p>Security update for squid</p> https://cve.radiocsirt.org/vuln/suse-su-2019:2975-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-18678 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: squid3, Ubuntu:18.04:LTS: squid3, Ubuntu:20.04:LTS: squid</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: squid3, Ubuntu:18.04:LTS: squid3, Ubuntu:20.04:LTS: squid</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-18678 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1391 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Squid ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen und um Anfragen zu manipulieren.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Squid ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen und um Anfragen zu manipulieren.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1391