CWE
20
Advisory Published
Updated

CVE-2014-3609: Input Validation

First published: Thu Sep 11 2014(Updated: )

HttpHdrRange.cc in Squid 3.x before 3.3.12 and 3.4.x before 3.4.6 allows remote attackers to cause a denial of service (crash) via a request with crafted "Range headers with unidentifiable byte-range values."

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Squid Web Proxy Cache=3.1
Squid Web Proxy Cache=3.1.0.1
Squid Web Proxy Cache=3.1.0.2
Squid Web Proxy Cache=3.1.0.3
Squid Web Proxy Cache=3.1.0.4
Squid Web Proxy Cache=3.1.0.5
Squid Web Proxy Cache=3.1.0.6
Squid Web Proxy Cache=3.1.0.7
Squid Web Proxy Cache=3.1.0.8
Squid Web Proxy Cache=3.1.0.9
Squid Web Proxy Cache=3.1.0.10
Squid Web Proxy Cache=3.1.0.11
Squid Web Proxy Cache=3.1.0.12
Squid Web Proxy Cache=3.1.0.13
Squid Web Proxy Cache=3.1.0.14
Squid Web Proxy Cache=3.1.0.15
Squid Web Proxy Cache=3.1.0.16
Squid Web Proxy Cache=3.1.0.17
Squid Web Proxy Cache=3.1.0.18
Squid Web Proxy Cache=3.1.1
Squid Web Proxy Cache=3.1.2
Squid Web Proxy Cache=3.1.3
Squid Web Proxy Cache=3.1.4
Squid Web Proxy Cache=3.1.5
Squid Web Proxy Cache=3.1.5.1
Squid Web Proxy Cache=3.1.6
Squid Web Proxy Cache=3.1.7
Squid Web Proxy Cache=3.1.8
Squid Web Proxy Cache=3.1.9
Squid Web Proxy Cache=3.1.10
Squid Web Proxy Cache=3.1.11
Squid Web Proxy Cache=3.1.12
Squid Web Proxy Cache=3.1.13
Squid Web Proxy Cache=3.1.14
Squid Web Proxy Cache=3.1.15
Squid Web Proxy Cache=3.2.0.1
Squid Web Proxy Cache=3.2.0.2
Squid Web Proxy Cache=3.2.0.3
Squid Web Proxy Cache=3.2.0.4
Squid Web Proxy Cache=3.2.0.5
Squid Web Proxy Cache=3.2.0.6
Squid Web Proxy Cache=3.2.0.7
Squid Web Proxy Cache=3.2.0.8
Squid Web Proxy Cache=3.2.0.9
Squid Web Proxy Cache=3.2.0.10
Squid Web Proxy Cache=3.2.0.11
Squid Web Proxy Cache=3.2.0.12
Squid Web Proxy Cache=3.2.0.13
Squid Web Proxy Cache=3.2.0.14
Squid Web Proxy Cache=3.2.0.15
Squid Web Proxy Cache=3.2.0.16
Squid Web Proxy Cache=3.2.0.17
Squid Web Proxy Cache=3.2.0.18
Squid Web Proxy Cache=3.2.0.19
Squid Web Proxy Cache=3.2.1
Squid Web Proxy Cache=3.2.2
Squid Web Proxy Cache=3.2.3
Squid Web Proxy Cache=3.2.4
Squid Web Proxy Cache=3.2.5
Squid Web Proxy Cache=3.2.6
Squid Web Proxy Cache=3.2.7
Squid Web Proxy Cache=3.2.8
Squid Web Proxy Cache=3.2.9
Squid Web Proxy Cache=3.2.10
Squid Web Proxy Cache=3.2.11
Squid Web Proxy Cache=3.2.12
Squid Web Proxy Cache=3.3.0
Squid Web Proxy Cache=3.3.0.2
Squid Web Proxy Cache=3.3.0.3
Squid Web Proxy Cache=3.3.1
Squid Web Proxy Cache=3.3.2
Squid Web Proxy Cache=3.3.3
Squid Web Proxy Cache=3.3.4
Squid Web Proxy Cache=3.3.5
Squid Web Proxy Cache=3.3.6
Squid Web Proxy Cache=3.3.7
Squid Web Proxy Cache=3.3.8
Squid Web Proxy Cache=3.3.9
Squid Web Proxy Cache=3.3.10
Squid Web Proxy Cache=3.3.11
Squid Web Proxy Cache=3.4.0.1
Squid Web Proxy Cache=3.4.0.2
Squid Web Proxy Cache=3.4.0.3
Squid Web Proxy Cache=3.4.1
Squid Web Proxy Cache=3.4.2
Squid Web Proxy Cache=3.4.3
Squid Web Proxy Cache=3.4.4
Squid Web Proxy Cache=3.4.5

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.

Frequently Asked Questions

  • What is the severity of CVE-2014-3609?

    CVE-2014-3609 has a severity rating that indicates it could lead to a denial of service on affected Squid cache servers.

  • How do I fix CVE-2014-3609?

    To fix CVE-2014-3609, upgrade to Squid versions 3.3.12, 3.4.6 or later.

  • Which versions are affected by CVE-2014-3609?

    CVE-2014-3609 affects Squid versions prior to 3.3.12 and 3.4.6.

  • What type of vulnerability is CVE-2014-3609?

    CVE-2014-3609 is a denial of service vulnerability caused by crafted Range headers.

  • Can CVE-2014-3609 be exploited remotely?

    Yes, CVE-2014-3609 can be exploited remotely by attackers sending specially crafted requests.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203