Jakarta Tomcat Directory Listing vulnerability
Jakarta Tomcat before 3.3.1a, when used with JDK 1.3.1 or earlier, allows remote attackers to list directories even with an index.html or other file present, or obtain unprocessed source code for a JSP file, via a URL containing a null character.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.apache.tomcat:tomcat | < 3.3.1a | 3.3.1a |
References
- https://nvd.nist.gov/vuln/detail/CVE-2003-0042
- https://exchange.xforce.ibmcloud.com/vulnerabilities/11194
- https://github.com/apache/tomcat
- http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1a
- http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1a/RELEASE-NOTES-3.3.1a.txt
- http://marc.info/?l=bugtraq&m=104394568616290&w=2
- http://secunia.com/advisories/7972
- http://secunia.com/advisories/7977
- http://www.ciac.org/ciac/bulletins/n-060.shtml
- http://www.debian.org/security/2003/dsa-246
- http://www.securityfocus.com/advisories/5111
- http://www.securityfocus.com/bid/6721
- Weakness (CWE)
CWE-22- Platform
- Java / Kotlin (Maven)
- Package
org.apache.tomcat:tomcat- Disclosed
- 29.04.2022
- Updated
- 11.10.2026 11:20
Sources and licenses
OSV / GitHub Advisory Database - GHSA-qfw2-wvrw-mvw4 - CC BY 4.0
Vulnerability history: org.apache.tomcat:tomcat
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 162
- First → latest
- 12.2018 08.2026
- Without a fix
- 20
- Exploited in attacks
- 1
Severity breakdown
- Critical 8
- High 40
- Medium 102
- Low 12
Disclosures per year
- 2018: 1
- 2019: 1
- 2020: 2
- 2021: 5
- 2022: 125
- 2023: 3
- 2024: 2
- 2025: 4
- 2026: 19
-
Jakarta Tomcat Directory Listing vulnerability this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.