CVE-2012-0022: Medium severity Apache Tomcat vulnerability

Published Jan 19, 2012
·
Updated

Apache Tomcat 5.5.x before 5.5.35, 6.x before 6.0.34, and 7.x before 7.0.23 uses an inefficient approach for handling parameters, which allows remote attackers to cause a denial of service (CPU consumption) via a request that contains many parameters and parameter values, a different vulnerability than CVE-2011-4858.

Other sources

From the upstream advisory [1]:

Analysis of the recent hash collision vulnerability identified unrelated inefficiencies with Apache Tomcat's handling of large numbers of parameters and parameter values. These inefficiencies could allow an attacker, via a specially crafted request, to cause large amounts of CPU to be used which in turn could create a denial of service. The issue was addressed by modifying the Tomcat parameter handling code to efficiently process large numbers of parameters and parameter values.

Upstream has released 7.0.23, 6.0.35 and 5.5.35 to correct this flaw. Earlier versions of Tomcat may also be affected.

[1] http://seclists.org/bugtraq/2012/Jan/111

Red Hat

Affected Software

95 affected componentsFixes available
maven/org.apache.tomcat:tomcat>=7.0.0<7.0.23
7.0.23
maven/org.apache.tomcat:tomcat>=6.0.0<6.0.34
6.0.34
maven/org.apache.tomcat:tomcat>=5.5.0<5.5.35
5.5.35
redhat/tomcat5<5.5.35
5.5.35
redhat/tomcat6<6.0.35
6.0.35
Apache Tomcat=5.5.0
Apache Tomcat=5.5.1
Apache Tomcat=5.5.2
Apache Tomcat=5.5.3
Apache Tomcat=5.5.4
Apache Tomcat=5.5.5
Apache Tomcat=5.5.6
Apache Tomcat=5.5.7
Apache Tomcat=5.5.8
Apache Tomcat=5.5.9
Apache Tomcat=5.5.10
Apache Tomcat=5.5.11
Apache Tomcat=5.5.12
Apache Tomcat=5.5.13
Apache Tomcat=5.5.14
Apache Tomcat=5.5.15
Apache Tomcat=5.5.16
Apache Tomcat=5.5.17
Apache Tomcat=5.5.18
Apache Tomcat=5.5.19
Apache Tomcat=5.5.20
Apache Tomcat=5.5.21
Apache Tomcat=5.5.22
Apache Tomcat=5.5.23
Apache Tomcat=5.5.24
Apache Tomcat=5.5.25
Apache Tomcat=5.5.26
Apache Tomcat=5.5.27
Apache Tomcat=5.5.28
Apache Tomcat=5.5.29
Apache Tomcat=5.5.30
Apache Tomcat=5.5.31
Apache Tomcat=5.5.32
Apache Tomcat=5.5.33
Apache Tomcat=5.5.34
Apache Tomcat=6.0
Apache Tomcat=6.0.0
Apache Tomcat=6.0.1
Apache Tomcat=6.0.2
Apache Tomcat=6.0.3
Apache Tomcat=6.0.4
Apache Tomcat=6.0.5
Apache Tomcat=6.0.6
Apache Tomcat=6.0.7
Apache Tomcat=6.0.8
Apache Tomcat=6.0.9
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=7.0.0
Apache Tomcat=7.0.0-beta
Apache Tomcat=7.0.1
Apache Tomcat=7.0.2
Apache Tomcat=7.0.3
Apache Tomcat=7.0.4
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

Event History

Jan 19, 2012
CVE Published
via MITRE·02:00 AM
Data Sourced
via MITRE·02:00 AM
Description
May 4, 2022
Advisory Published
via GitHub·12:27 AM

Frequently Asked Questions

1

What is the severity of CVE-2012-0022?

CVE-2012-0022 has a high severity rating as it can lead to denial of service by consuming CPU resources.

2

How do I fix CVE-2012-0022?

To fix CVE-2012-0022, upgrade to Apache Tomcat version 5.5.35, 6.0.34, or 7.0.23 or later.

3

What versions of Apache Tomcat are affected by CVE-2012-0022?

CVE-2012-0022 affects Apache Tomcat versions 5.5.x before 5.5.35, 6.x before 6.0.34, and 7.x before 7.0.23.

4

What type of attack does CVE-2012-0022 facilitate?

CVE-2012-0022 facilitates denial of service attacks through the submission of a large number of parameters in requests.

5

Is CVE-2012-0022 a remote vulnerability?

Yes, CVE-2012-0022 is a remote vulnerability allowing attackers to exploit it without physical access.

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