CVE-2011-3190: High severity tomcat vulnerability

Published Aug 31, 2011
·
Updated

Certain AJP protocol connector implementations in Apache Tomcat 7.0.0 through 7.0.20, 6.0.0 through 6.0.33, 5.5.0 through 5.5.33, and possibly other versions allow remote attackers to spoof AJP requests, bypass authentication, and obtain sensitive information by causing the connector to interpret a request body as a new request.

Affected Software

88 affected componentsFixes available
maven/org.apache.tomcat:tomcat>=5.0.0<=5.5.33
5.5.34
maven/org.apache.tomcat:tomcat>=6.0.0<=6.0.33
6.0.34
maven/org.apache.tomcat:tomcat>=7.0.0<=7.0.20
7.0.21
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.16
Apache Tomcat=7.0.17
Apache Tomcat=7.0.19
Apache Tomcat=7.0.20
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=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

Event History

Aug 31, 2011
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
May 14, 2022
Advisory Published
via GitHub·01:17 AM

Frequently Asked Questions

1

What is the severity of CVE-2011-3190?

CVE-2011-3190 has been classified as a critical severity vulnerability due to potential unauthorized access to sensitive information.

2

How do I fix CVE-2011-3190?

To fix CVE-2011-3190, upgrade your Apache Tomcat version to 5.5.34, 6.0.34, or 7.0.21 or later.

3

What versions of Apache Tomcat are affected by CVE-2011-3190?

CVE-2011-3190 affects Apache Tomcat versions 5.5.0 through 5.5.33, 6.0.0 through 6.0.33, and 7.0.0 through 7.0.20.

4

What type of attack is possible due to CVE-2011-3190?

CVE-2011-3190 allows remote attackers to spoof AJP requests, bypass authentication, and potentially access sensitive information.

5

Is there a workaround for CVE-2011-3190?

While the best solution is to upgrade your Apache Tomcat, a temporary workaround involves restricting access to the AJP connectors.

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