high
7.5
CWE
190
Advisory Published
CVE Published
Updated

CVE-2017-12425: Integer Overflow

First published: Tue Aug 01 2017(Updated: )

An issue was discovered in Varnish HTTP Cache 4.0.1 through 4.0.4, 4.1.0 through 4.1.7, 5.0.0, and 5.1.0 through 5.1.2. A wrong if statement in the varnishd source code means that particular invalid requests from the client can trigger an assert, related to an Integer Overflow. This causes the varnishd worker process to abort and restart, losing the cached contents in the process. An attacker can therefore crash the varnishd worker process on demand and effectively keep it from serving content - a Denial-of-Service attack. The specific source-code filename containing the incorrect statement varies across releases.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
redhat/varnish<4.0.5
4.0.5
redhat/varnish<4.1.8
4.1.8
redhat/varnish<5.1.3
5.1.3
Varnish Enterprise=4.0.2-rc-1
Varnish Enterprise=4.0.3-rc-1
Varnish Enterprise=4.0.3-rc-2
Varnish Enterprise=4.0.3-rc-2-proper
Varnish Enterprise=4.0.3-rc-3
Varnish Cache=4.0.1
Varnish Cache=4.0.2
Varnish Cache=4.0.3
Varnish Cache=4.0.4
Varnish Enterprise=4.1.0
Varnish Enterprise=4.1.0-beta1
Varnish Enterprise=4.1.0-technology_preview1
Varnish Enterprise=4.1.1
Varnish Enterprise=4.1.1-beta1
Varnish Enterprise=4.1.1-beta2
Varnish Enterprise=4.1.2
Varnish Enterprise=4.1.2-beta1
Varnish Enterprise=4.1.2-beta2
Varnish Enterprise=4.1.3
Varnish Enterprise=4.1.3-beta1
Varnish Enterprise=4.1.3-beta2
Varnish Enterprise=4.1.4
Varnish Enterprise=4.1.4-beta1
Varnish Enterprise=4.1.4-beta2
Varnish Enterprise=4.1.4-beta3
Varnish Enterprise=4.1.5
Varnish Enterprise=4.1.5-beta1
Varnish Enterprise=4.1.5-beta2
Varnish Enterprise=4.1.6
Varnish Enterprise=4.1.7
Varnish Cache=5.0.0
Varnish Cache=5.1.0
Varnish Cache=5.1.1
Varnish Cache=5.1.2

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

Frequently Asked Questions

  • What is the severity of CVE-2017-12425?

    CVE-2017-12425 is classified as a medium severity vulnerability due to its potential to cause application crashes.

  • How do I fix CVE-2017-12425?

    To fix CVE-2017-12425, upgrade Varnish HTTP Cache to version 4.0.5, 4.1.8, or 5.1.3 or later.

  • Which versions of Varnish HTTP Cache are affected by CVE-2017-12425?

    CVE-2017-12425 affects Varnish HTTP Cache versions 4.0.1 through 4.0.4, 4.1.0 through 4.1.7, and versions 5.0.0 and 5.1.0 through 5.1.2.

  • What kind of issue does CVE-2017-12425 represent?

    CVE-2017-12425 represents a coding error that can cause an integer overflow and subsequent application assertion failures.

  • What is the impact of CVE-2017-12425 on users?

    Users of affected Varnish versions may experience potential system instability and unexpected crashes when processing invalid client requests.

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