CVE-2002-2006: Medium severity Apache Tomcat vulnerability

Published Dec 31, 2002
·
Updated

The default installation of Apache Tomcat 4.0 through 4.1 and 3.0 through 3.3.1 allows remote attackers to obtain the installation path and other sensitive system information via the (1) SnoopServlet or (2) TroubleShooter example servlets.

Affected Software

16 affected componentsFixes available
maven/org.apache.tomcat:tomcat>=3.0<3.3a
3.3a
maven/org.apache.tomcat:tomcat>=4.0.0<4.1.0
4.1.0
Apache Tomcat=3.0
Apache Tomcat=3.1
Apache Tomcat=3.1.1
Apache Tomcat=3.2
Apache Tomcat=3.2.1
Apache Tomcat=3.2.3
Apache Tomcat=3.2.4
Apache Tomcat=3.3
Apache Tomcat=3.3.1
Apache Tomcat=4.0.0
Apache Tomcat=4.0.1
Apache Tomcat=4.0.2
Apache Tomcat=4.0.3
Apache Tomcat=4.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 3.3a
  2. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat to a version that resolves this vulnerability.

    Fixed in 4.1.0

Event History

Dec 31, 2002
CVE Published
via NVD·05:00 AM
Data Sourced
via NVD·05:00 AM
DescriptionSeverityAffected Software
Jul 14, 2005
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Apr 30, 2022
Advisory Published
via GitHub·06:22 PM

Frequently Asked Questions

1

What is the severity of CVE-2002-2006?

CVE-2002-2006 is considered a medium severity vulnerability due to its potential exposure of sensitive system information.

2

How do I fix CVE-2002-2006?

To fix CVE-2002-2006, upgrade to Apache Tomcat version 3.3a or later for versions 3.0 to 3.3.1, and to version 4.1.0 or later for versions 4.0.0 to 4.1.

3

What versions are affected by CVE-2002-2006?

CVE-2002-2006 affects Apache Tomcat versions 3.0 through 4.1, including various sub-versions in-between.

4

How does CVE-2002-2006 impact Apache Tomcat security?

CVE-2002-2006 allows remote attackers to obtain the installation path and sensitive system information, potentially leading to further exploitation.

5

Is there a workaround for CVE-2002-2006?

While the best approach is to upgrade to a patched version, a temporary workaround may include disabling the SnoopServlet and TroubleShooter example servlets.

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