CVE-2007-5333: Exposure of Sensitive Information in Apache Tomcat

org.apache.tomcat:tomcat Updated 02 Oct 2025

Summary

01/05/2022
Yes i
Moderate
Not published

CVE-2007-5333: Exposure of Sensitive Information in Apache Tomcat. Affects org.apache.tomcat:tomcat across 3 version ranges.

>= 4.1.0, < 4.1.37 >= 5.5.0, < 5.5.26 >= 6.0.0, < 6.0.15

Fixed in 4.1.37, 5.5.26 or 6.0.15, depending on the release line you run. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Tomcat is an open-source web server and servlet container that is widely used for hosting Java-based web applications. It provides a robust and scalable platform for running Java web applications, with features such as HTTP/2 support, SSL/TLS encryption, and session management. However, versions 6.0.0 through 6.0.14, 5.5.0 through 5.5.25, and 4.1.0 through 4.1.36 of Apache Tomcat are vulnerable to an information exposure issue.

Vulnerability Detail

The vulnerability in Apache Tomcat allows remote attackers to obtain sensitive information, such as session IDs, by exploiting improper handling of double quote characters and encoded backslash sequences in a cookie value. This can lead to session hijacking attacks, where an attacker gains unauthorized access to a user's session and performs actions on their behalf. The issue is a result of an incomplete fix for CVE-2007-3385.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 4.1.0, < 4.1.37 4.1.37
  • >= 5.5.0, < 5.5.26 5.5.26
  • >= 6.0.0, < 6.0.15 6.0.15

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

If upgrading to a fixed version is not immediately possible, a workaround can be implemented by modifying the affected code to properly handle double quote characters and encoded backslash sequences in cookie values. The specific changes required will depend on the application and how cookies are processed. It is recommended to consult the Apache Tomcat documentation or seek assistance from a qualified developer to implement the necessary changes.

Conclusion

In conclusion, the vulnerability in Apache Tomcat allows remote attackers to obtain sensitive information and potentially perform session hijacking attacks. It is important to upgrade to a fixed version of Apache Tomcat or implement the recommended workaround to mitigate the risk. For further support on 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 widely used for hosting Java-based web applications.

The vulnerability allows remote attackers to obtain sensitive information, such as session IDs, which can lead to session hijacking attacks.

To fix this vulnerability, it is recommended to upgrade to a fixed version of Apache Tomcat.

If upgrading to a fixed version is not immediately possible, a workaround can be implemented by modifying the affected code.

You can find more information about this vulnerability in the Apache Tomcat documentation or by contacting the Apache Tomcat community.

Related vulnerabilities

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

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 4.1.0, < 4.1.37 4.1.37
  • >= 5.5.0, < 5.5.26 5.5.26
  • >= 6.0.0, < 6.0.15 6.0.15

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. 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