CVE-2005-4836
Apache Tomcat allows remote attackers to read JSP source files
Overview
Description
The HTTP/1.1 connector in Apache Tomcat 4.1.15 through 4.1.40 does not reject NULL bytes in a URL when allowLinking is configured, which allows remote attackers to read JSP source files and obtain sensitive information.
Source: OX vulnerability database
Severity
7.8 · HIGH
CVSS 2.0 base score, scored by NVD.
- Access vector
- Network
- Access complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/I:N/A:N
Weakness: CWE-200
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Maven | org.apache.tomcat:tomcat | >=4.1.15, <=4.1.40 | No fix yet |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- tomcat.apache.org http://tomcat.apache.org/security-4.html
- www.securityfocus.com http://www.securityfocus.com/bid/28483
- lists.apache.org https://lists.apache.org/thread.html/29dc6c2b625789e70a9c4756b5a327e6547273ff8bde7e0327af48c5%40%3Cdev.tomcat.apache.org%3E
- lists.apache.org https://lists.apache.org/thread.html/29dc6c2b625789e70a9c4756b5a327e6547273ff8bde7e0327af48c5@%3Cdev.tomcat.apache.org%3E
- lists.apache.org https://lists.apache.org/thread.html/c62b0e3a7bf23342352a5810c640a94b6db69957c5c19db507004d74%40%3Cdev.tomcat.apache.org%3E
- lists.apache.org https://lists.apache.org/thread.html/c62b0e3a7bf23342352a5810c640a94b6db69957c5c19db507004d74@%3Cdev.tomcat.apache.org%3E
- lists.apache.org https://lists.apache.org/thread.html/rb71997f506c6cc8b530dd845c084995a9878098846c7b4eacfae8db3%40%3Cdev.tomcat.apache.org%3E
- lists.apache.org https://lists.apache.org/thread.html/rb71997f506c6cc8b530dd845c084995a9878098846c7b4eacfae8db3@%3Cdev.tomcat.apache.org%3E
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2005-4836
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.