CVE-2002-1148: Infoleak

Published Oct 11, 2002
·
Updated

The default servlet (org.apache.catalina.servlets.DefaultServlet) in Tomcat 4.0.4 and 4.1.10 and earlier allows remote attackers to read source code for server files via a direct request to the servlet.

Other sources

The default servlet (org.apache.catalina.servlets.DefaultServlet) in Tomcat 4.0.4 and 4.1.10 and earlier allows remote attackers to read source code for server files via a direct request to the servlet.

Affected Software

21 affected componentsFixes available
maven/org.apache.tomcat:tomcat>=4.1.0<=4.1.10
4.1.12
maven/org.apache.tomcat:tomcat>=4.0.0<=4.0.4
4.0.5
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.2-beta2
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.0.4
Apache Tomcat=4.1.0
Apache Tomcat=4.1.3-beta
Apache Tomcat=4.1.9-beta
Apache Tomcat=4.1.10

Remediation

Event History

Oct 11, 2002
CVE Published
via NVD·04:00 AM
Sep 1, 2004
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Apr 30, 2022
Advisory Published
via GitHub·06:20 PM

Frequently Asked Questions

1

What is the severity of CVE-2002-1148?

CVE-2002-1148 is considered a critical vulnerability as it allows unauthorized access to server source code.

2

How do I fix CVE-2002-1148?

To fix CVE-2002-1148, upgrade to Apache Tomcat version 4.1.12 or higher for the 4.x branch, and 4.0.5 or higher for the 4.0.x branch.

3

Which versions of Apache Tomcat are affected by CVE-2002-1148?

Affected versions of Apache Tomcat include 3.0, 3.1, 3.2, 4.0.0 through 4.1.10, and related beta versions.

4

What are the risks of not addressing CVE-2002-1148?

Failing to address CVE-2002-1148 can lead to significant data breaches as attackers can access sensitive server files.

5

How can CVE-2002-1148 be exploited?

CVE-2002-1148 can be exploited by making a direct request to the default servlet, enabling remote attackers to read source code.

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