CVE-2014-0230: High severity Apache Tomcat vulnerability

Published Feb 10, 2015
·
Updated

Apache Tomcat 6.x before 6.0.44, 7.x before 7.0.55, and 8.x before 8.0.9 does not properly handle cases where an HTTP response occurs before finishing the reading of an entire request body, which allows remote attackers to cause a denial of service (thread consumption) via a series of aborted upload attempts.

Other sources

When a response for a request with a request body is returned to the user agent before the request body is fully read, by default Tomcat swallows the remaining request body so that the next request on the connection may be processed. There was no limit to the size of request body that Tomcat would swallow. This permitted a limited Denial of Service as Tomcat would never close the connection and a processing thread would remain allocated to the connection.

Upstream fix:

http://svn.apache.org/viewvc?view=revision&revision=1603781 http://svn.apache.org/viewvc?view=revision&revision=1603811 http://svn.apache.org/viewvc?view=revision&revision=1609176 http://svn.apache.org/viewvc?view=revision&revision=1659295

Red Hat

Affected Software

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

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 8.0.9
  2. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 7.0.55
  3. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 6.0.44
  4. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 6.0.44
  5. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 7.0.55
  6. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.0.9
  7. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 6.0.44
  8. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 7.0.55
  9. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 8.0.9

Event History

Feb 10, 2015
Data Sourced
via Red Hat·04:38 PM
DescriptionSeverityAffected Software
Jun 7, 2015
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
May 14, 2022
Advisory Published
via GitHub·01:10 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2014-0230?

CVE-2014-0230 has a medium severity rating due to its potential to cause denial of service attacks.

2

How do I fix CVE-2014-0230?

To fix CVE-2014-0230, upgrade to Apache Tomcat version 6.0.44 or later, 7.0.55 or later, or 8.0.9 or later.

3

What versions of Apache Tomcat are affected by CVE-2014-0230?

CVE-2014-0230 affects Apache Tomcat versions 6.x before 6.0.44, 7.x before 7.0.55, and 8.x before 8.0.9.

4

Can CVE-2014-0230 be exploited remotely?

Yes, CVE-2014-0230 can be exploited remotely by attackers, allowing them to execute denial of service attacks.

5

What are the implications of CVE-2014-0230 for my web applications?

The implications of CVE-2014-0230 include thread consumption and potential service disruption for web applications running on the affected versions of Tomcat.

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