medium
5
CWE
190 400 189
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2014-0075: Integer Overflow

First published: Wed Mar 05 2014(Updated: )

Apache Tomcat did not limit the length of chunk sizes when using chunked transfer coding. A remote attacker could use this flaw to perform a denial of service attack against Tomcat, by streaming an unlimited quantity of data, leading to consumption of server resources.

Credit: secalert@redhat.com secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
maven/org.apache.tomcat:tomcat>=8.0.0<8.0.4
8.0.4
maven/org.apache.tomcat:tomcat>=7.0.0<7.0.53
7.0.53
maven/org.apache.tomcat:tomcat<6.0.40
6.0.40
redhat/tomcat<7.0.53
7.0.53
redhat/tomcat<6.0.41
6.0.41
Tomcat=7.0.0
Tomcat=7.0.0-beta
Tomcat=7.0.1
Tomcat=7.0.2
Tomcat=7.0.2-beta
Tomcat=7.0.3
Tomcat=7.0.4
Tomcat=7.0.4-beta
Tomcat=7.0.5
Tomcat=7.0.6
Tomcat=7.0.7
Tomcat=7.0.8
Tomcat=7.0.9
Tomcat=7.0.10
Tomcat=7.0.11
Tomcat=7.0.12
Tomcat=7.0.13
Tomcat=7.0.14
Tomcat=7.0.15
Tomcat=7.0.16
Tomcat=7.0.17
Tomcat=7.0.18
Tomcat=7.0.19
Tomcat=7.0.20
Tomcat=7.0.21
Tomcat=7.0.22
Tomcat=7.0.23
Tomcat=7.0.24
Tomcat=7.0.25
Tomcat=7.0.26
Tomcat=7.0.27
Tomcat=7.0.28
Tomcat=7.0.29
Tomcat=7.0.30
Tomcat=7.0.31
Tomcat=7.0.32
Tomcat=7.0.33
Tomcat=7.0.34
Tomcat=7.0.35
Tomcat=7.0.36
Tomcat=7.0.37
Tomcat=7.0.38
Tomcat=7.0.39
Tomcat=7.0.40
Tomcat=7.0.41
Tomcat=7.0.42
Tomcat=7.0.43
Tomcat=7.0.44
Tomcat=7.0.45
Tomcat=7.0.46
Tomcat=7.0.47
Tomcat=7.0.48
Tomcat=7.0.49
Tomcat=7.0.50
Tomcat=7.0.52
Tomcat=8.0.0-rc1
Tomcat=8.0.0-rc10
Tomcat=8.0.0-rc2
Tomcat=8.0.0-rc5
Tomcat=8.0.1
Tomcat=8.0.3
Tomcat<=6.0.39
Tomcat=6
Tomcat=6.0
Tomcat=6.0.0
Tomcat=6.0.0-alpha
Tomcat=6.0.1
Tomcat=6.0.1-alpha
Tomcat=6.0.2
Tomcat=6.0.2-alpha
Tomcat=6.0.2-beta
Tomcat=6.0.3
Tomcat=6.0.4
Tomcat=6.0.4-alpha
Tomcat=6.0.5
Tomcat=6.0.6
Tomcat=6.0.6-alpha
Tomcat=6.0.7
Tomcat=6.0.7-alpha
Tomcat=6.0.7-beta
Tomcat=6.0.8
Tomcat=6.0.8-alpha
Tomcat=6.0.9
Tomcat=6.0.9-beta
Tomcat=6.0.10
Tomcat=6.0.11
Tomcat=6.0.12
Tomcat=6.0.13
Tomcat=6.0.14
Tomcat=6.0.15
Tomcat=6.0.16
Tomcat=6.0.17
Tomcat=6.0.18
Tomcat=6.0.19
Tomcat=6.0.20
Tomcat=6.0.24
Tomcat=6.0.26
Tomcat=6.0.27
Tomcat=6.0.28
Tomcat=6.0.29
Tomcat=6.0.30
Tomcat=6.0.31
Tomcat=6.0.32
Tomcat=6.0.33
Tomcat=6.0.35
Tomcat=6.0.36
Tomcat=6.0.37

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-2014-0075?

    CVE-2014-0075 has a severity rating that indicates a potential denial of service risk due to its exploitation.

  • How do I fix CVE-2014-0075?

    To remediate CVE-2014-0075, upgrade your Apache Tomcat installation to versions 6.0.40, 7.0.53, or 8.0.4 and later.

  • What software is affected by CVE-2014-0075?

    CVE-2014-0075 affects multiple versions of Apache Tomcat, specifically versions 6.0.0 to 6.0.39, 7.0.0 to 7.0.52, and 8.0.0-rc1 to 8.0.3.

  • Can CVE-2014-0075 lead to data loss?

    CVE-2014-0075 primarily presents a denial of service risk, which may indirectly affect data availability but does not directly cause data loss.

  • Is CVE-2014-0075 related to resource exhaustion?

    Yes, CVE-2014-0075 can lead to resource exhaustion on the server through uncontrolled chunked transfer coding.

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