critical
9.6
CWE
79 20 444
Advisory Published
CVE Published
Updated

CVE-2020-15810: XSS

First published: Mon Aug 24 2020(Updated: )

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.

Credit: cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
debian/squid<=4.6-1+deb10u3<=4.6-1<=4.12-1
4.13-1
4.6-1+deb10u4
Squid-Cache Squid<4.13
Squid-Cache Squid>=5.0<5.0.4
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=20.04
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Fedoraproject Fedora=31
Fedoraproject Fedora=32
Fedoraproject Fedora=33
openSUSE Leap=15.1
openSUSE Leap=15.2
IBM Security Guardium<=10.5
IBM Security Guardium<=10.6
IBM Security Guardium<=11.0
IBM Security Guardium<=11.1
IBM Security Guardium<=11.2
IBM Security Guardium<=11.3
debian/squid
4.13-10+deb11u3
5.7-2+deb12u2
6.10-1

Remedy

http://www.squid-cache.org/Versions/v4/changesets/SQUID-2020_10.patch

Remedy

https://github.com/squid-cache/squid/commit/9c8e2a71aa1d3c159a319d9365c346c48dc783a5

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the vulnerability ID for this Squid-Cache vulnerability?

    The vulnerability ID for this Squid-Cache vulnerability is CVE-2020-15810.

  • What is the severity of CVE-2020-15810?

    CVE-2020-15810 has a severity rating of 9.6 (Critical).

  • What is the affected software for CVE-2020-15810?

    The affected software for CVE-2020-15810 includes Squid versions before 4.13 and 5.x before 5.0.4, as well as IBM Security Guardium versions up to 11.3.

  • How does CVE-2020-15810 impact HTTP and HTTPS traffic?

    CVE-2020-15810 can lead to successful HTTP Request Smuggling attacks against HTTP and HTTPS traffic, resulting in cache poisoning.

  • Where can I find more information about CVE-2020-15810?

    You can find more information about CVE-2020-15810 in the following references: [1](http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00012.html), [2](http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00017.html), [3](https://github.com/squid-cache/squid/security/advisories/GHSA-3365-q9qx-f98m).

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203