CVE-2011-1183: Access control bypass in Apache Tomcat

org.apache.tomcat:tomcat Updated 02 Oct 2025

Summary

14/05/2022
Yes i
Moderate
Not published

CVE-2011-1183: Access controll bypass in Apache Tomcat. Affects org.apache.tomcat:tomcat versions >= 7.0.11, < 7.0.12. Fixed in 7.0.12. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Apache Tomcat is an open-source web server and servlet container that is used to deploy Java-based web applications. It provides a Java Servlet and JavaServer Pages (JSP) environment for running web applications. The vulnerability in Apache Tomcat version 7.0.11 allows remote attackers to bypass access restrictions when the web.xml file does not have a login configuration. This vulnerability exists due to an incorrect fix for CVE-2011-1088 and CVE-2011-1419.

Vulnerability Detail

The vulnerability allows remote attackers to bypass intended access restrictions by sending HTTP requests to a meta-data complete web application. When the web.xml file does not have a login configuration, Apache Tomcat 7.0.11 does not follow security constraints. This can lead to unauthorized access to sensitive resources and potential data breaches. The vulnerability was introduced in version 7.0.11 and was fixed in version 7.0.12.

How To Fix

Minimum fixed version

7.0.12

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to the latest version of Apache Tomcat is not feasible, you can apply a workaround by manually configuring the login configuration in the web.xml file. Add the necessary login configuration elements to enforce access controls and prevent unauthorized access. Here is an example of how the login configuration can be added:

<login-config>
  <auth-method>BASIC</auth-method>
  <realm-name>Restricted Area</realm-name>
</login-config>

Make sure to customize the auth-method and realm-name according to your application's requirements.

Conclusion

The access control bypass vulnerability in Apache Tomcat version 7.0.11 can allow remote attackers to bypass intended access restrictions and gain unauthorized access to sensitive resources. It is crucial to upgrade to Apache Tomcat version 7.0.12 or later to fix this vulnerability. If upgrading is not possible, applying a workaround by manually configuring the login configuration in the web.xml file can help mitigate the risk. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.tomcat:tomcat →

Share this vulnerability

FAQ

Apache Tomcat is an open-source web server and servlet container that is used to deploy Java-based web applications. It provides a Java Servlet and JavaServer Pages (JSP) environment for running web applications.

The vulnerability allows remote attackers to bypass access restrictions and potentially gain unauthorized access to sensitive resources. This can lead to data breaches and compromise the security of the affected web application.

To fix this vulnerability, it is recommended to upgrade to Apache Tomcat version 7.0.12 or later. This version includes the correct fix for the access control bypass issue. Alternatively, you can apply a workaround by manually configuring the login configuration in the web.xml file.

Yes, if upgrading to the latest version of Apache Tomcat is not feasible, you can apply a workaround by manually configuring the login configuration in the web.xml file. This will help enforce access controls and prevent unauthorized access.

You can download the latest version of Apache Tomcat from the official Apache Tomcat website (https://tomcat.apache.org/). Make sure to choose the appropriate version for your operating system and follow the installation instructions provided.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.tomcat:tomcat.

How To Fix

Minimum fixed version

7.0.12

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.