CVE-2009-0033: Input Validation

Published Jun 5, 2009
·
Updated

Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when the Java AJP connector and modjk load balancing are used, allows remote attackers to cause a denial of service (application outage) via a crafted request with invalid headers, related to temporary blocking of connectors that have encountered errors, as demonstrated by an error involving a malformed HTTP Host header.

Affected Software

90 affected components
maven/org.apache.tomcat:tomcat>=6.0.0<=6.0.18
maven/org.apache.tomcat:tomcat>=5.5.0<=5.5.27
maven/org.apache.tomcat:tomcat>=4.1.0<=4.1.39
Apache Tomcat=4.1.0
Apache Tomcat=4.1.1
Apache Tomcat=4.1.2
Apache Tomcat=4.1.3
Apache Tomcat=4.1.3-beta
Apache Tomcat=4.1.4
Apache Tomcat=4.1.5
Apache Tomcat=4.1.6
Apache Tomcat=4.1.7
Apache Tomcat=4.1.8
Apache Tomcat=4.1.9
Apache Tomcat=4.1.9-beta
Apache Tomcat=4.1.10
Apache Tomcat=4.1.11
Apache Tomcat=4.1.12
Apache Tomcat=4.1.13
Apache Tomcat=4.1.14
Apache Tomcat=4.1.15
Apache Tomcat=4.1.16
Apache Tomcat=4.1.17
Apache Tomcat=4.1.18
Apache Tomcat=4.1.19
Apache Tomcat=4.1.20
Apache Tomcat=4.1.21
Apache Tomcat=4.1.22
Apache Tomcat=4.1.23
Apache Tomcat=4.1.24
Apache Tomcat=4.1.25
Apache Tomcat=4.1.26
Apache Tomcat=4.1.27
Apache Tomcat=4.1.28
Apache Tomcat=4.1.29
Apache Tomcat=4.1.30
Apache Tomcat=4.1.31
Apache Tomcat=4.1.32
Apache Tomcat=4.1.33
Apache Tomcat=4.1.34
Apache Tomcat=4.1.35
Apache Tomcat=4.1.36
Apache Tomcat=4.1.37
Apache Tomcat=4.1.38
Apache Tomcat=4.1.39
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=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

Event History

Jun 5, 2009
CVE Published
via MITRE·03:25 PM
Data Sourced
via MITRE·03:25 PM
Description
May 2, 2022
Advisory Published
via GitHub·03:12 AM

Frequently Asked Questions

1

What is the severity of CVE-2009-0033?

CVE-2009-0033 has a high severity rating as it can cause denial of service through a crafted request.

2

How do I fix CVE-2009-0033?

To fix CVE-2009-0033, upgrade Apache Tomcat to a version beyond 6.0.18, 5.5.27, or 4.1.39.

3

Which versions of Apache Tomcat are affected by CVE-2009-0033?

CVE-2009-0033 affects Apache Tomcat versions 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18.

4

What type of attack does CVE-2009-0033 facilitate?

CVE-2009-0033 facilitates denial of service attacks that can lead to application outages.

5

Is there a workaround for CVE-2009-0033 if I can't upgrade?

While upgrading is the best solution for CVE-2009-0033, temporary measures include restricting access to the AJP connector.

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